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

Implicit parser specification #28

Closed
zgornel opened this issue Mar 5, 2020 · 0 comments
Closed

Implicit parser specification #28

zgornel opened this issue Mar 5, 2020 · 0 comments
Assignees

Comments

@zgornel
Copy link
Owner

zgornel commented Mar 5, 2020

The ability to select parser or parsing modes from a given text - i.e. parser detection stage (with default must exist)
In the request, the preparser should have a similar name i.e. pre_parser
This parser should access all available parsers

Examples:

  • noop> text noop mode, text is the actual query sent to db, searchers
  • nlp> some thext that can be nlp'd NLP mode
  • imp> https://julialang.org/v2/img/logo.svg` image mode
  • db> col1:value AND col2:[min, max]` juliadb mode
  • index> "index_1":"something embeddable" specify index and some text that the embedder of a searcher will recognize (i.e. simple text, a link to an image etc)

Ideea:
whatever query is sent gets triaged by an initial pre-parserthat looks for the pattern r"[a-zA-Z]+>"
and if found, selects the parser. A default has to exist, most probably noop_parser

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

No branches or pull requests

1 participant