[
https://issues.apache.org/jira/browse/BLUR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620517#comment-13620517
]
Aaron McCurry commented on BLUR-64:
-----------------------------------
Good questions.
1. If ScoreType is generated in 0.1.5 by that thrift definition file, then we
should keep the generated version.
2. Yes, everything should be moved to blur-query and the o.a.b.l.search package
should not exist in blur-core anymore. Where the there is overlapping
functionality between what is in blur-core and blur-query go with the version
implemented in blur-query.
3. I only mean that if we create a cache of TableContext for use with query
parsing (so we don't have to create the heavy object for every query) we should
create the object on startup/enabling the table/first use whatever is easiest.
And we should remove the object from the cache when a table is disabled.
That's all I meant.
Thanks Gagan!
> Update to use the new SuperQueryParser
> --------------------------------------
>
> Key: BLUR-64
> URL: https://issues.apache.org/jira/browse/BLUR-64
> Project: Apache Blur
> Issue Type: Improvement
> Affects Versions: 0.1.5
> Reporter: Aaron McCurry
> Fix For: 0.1.5
>
>
> In the 0.2-dev branch and the blur-query project there is a updated
> SuperQueryParser class that should be used in place of the legacy
> SuperQueryParser that is found in the blur-core project.
> NOTE: The blur-query project has already been merged into the 0.1.5 branch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
