FiloDB
FiloDB copied to clipboard
fix(query): correcly escape LogicalPlan-to-String backslashes
Pull Request checklist
- [x] The commit(s) message(s) follows the contribution guidelines ?
- [x] Tests for the changes have been added (for bug fixes / features) ?
- [ ] Docs have been added / updated (for bug fixes / features) ?
Currently, escape characters themselves may not be correctly escaped when LogicalPlan
s are converted to String
s. This may cause e.g. parse errors when plans are converted to String
s then sent remotely. This PR adds the correct escape characters to all miscellaneous function args; these may contain regex and require backslash escapes.