Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pre_parse filters are not particularly useful at the moment. #186

Open
danielrichman opened this issue Jun 28, 2012 · 2 comments
Open

pre_parse filters are not particularly useful at the moment. #186

danielrichman opened this issue Jun 28, 2012 · 2 comments

Comments

@danielrichman
Copy link
Member

Since we changed to having config in a YAML file pre-parse filters can't be easily set at runtime, so while it is possible to add one and restart the daemon, this could be better. There have been exactly zero uses for a pre parse filter so far though.

Also relevant (sort of): default_config has suffered the same fate. Similarly has not had any use. Could drop this feature from the parser tbh; would simplify the parse function.

@adamgreig
Copy link
Member

default_config has been removed from the parser

@danielrichman
Copy link
Member Author

Having just had to use a pre_filter (remove 0x00s from a string with UKHAS therefore refused to even contemplate parsing): feature request - ability to specify pre_filters in couch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants