-
Notifications
You must be signed in to change notification settings - Fork 3
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
Expand Search::Query to "auto-correct" #1
Comments
Hi Clint, I'd be happy to work with you on getting an ElasticSearch Dialect into Search::Query. It's been on my todo list. Does the 'sloppy' param option to Parser->new() do approximately what you're after? |
Hi Peter thanks for responding.
And I'd be more than happy to help you with that. I don't know how well
Oh I hadn't seen that. That's good. QueryParser goes a bit further - it Also, it gives the user some control over what is allowed in the query The various syntaxes you support may already do that - I haven't had a clint |
You can whitelist supported fields in the Parser->new constructor. I added a 'fixup' feature here: Let me know if that does what you had in mind. |
Hiya Peter On Sat, 2012-08-11 at 10:27 -0700, Peter Karman wrote:
Great
I apologise for having opened this issue at a moment when I've got so I'll be able to come back to this in September - marked in my diary :) thanks clint |
Clinton Gormley wrote on 8/13/12 2:02 AM:
No worries - sounds good. Peter Karman . http://peknet.com/ . peter@peknet.com |
0.22 was just pushed to CPAN with the 'fixup' feature. |
Hi Peter
Search::Query looks interesting. I wrote something related for ElasticSearch: https://metacpan.org/module/ElasticSearch::QueryParser.
One of the reasons for writing it was that ElasticSearch throws an error if the search string is malformed, eg
(foo
. By default, my module tries to fix up the query to be "legal", but it's not as flexible etc as it should be.If you were to expand Search::Query to do something similar, I'd prefer to ditch my module and replace it with yours. What do you think?
clint
The text was updated successfully, but these errors were encountered: