[
https://issues.apache.org/jira/browse/BLUR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619883#comment-13619883
]
Gagan Deep Juneja commented on BLUR-64:
---------------------------------------
I agree with you. I have some more points to discuss.
1. There are two versions of ScoreType.java class. one is generated through
thrift which is used at many places and another one is we created in 0.2. So
which should we keep. It doesn't impact a lot because both are having same enum
definition. But need to have only one to make consistency.
2. org.apache.blur.lucene.search package exists in both blur-core and
blur-query modules. Sholdn't we merge both in blur-query module only?
3. In IndexManager class I used TableContext class's create method to create
cache and TableContext object as well. I didn't understand here the use of
enabling and disabling table which you mentioned in the previous reply.
Regards,
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
