[jira] [Commented] (LUCENE-2899) Add OpenNLP Analysis capabilities as a module
[ https://issues.apache.org/jira/browse/LUCENE-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486242#comment-13486242 ] Phani Vempaty commented on LUCENE-2899: --- Would there be a patch for 4.0 as it is released. > Add OpenNLP Analysis capabilities as a module > - > > Key: LUCENE-2899 > URL: https://issues.apache.org/jira/browse/LUCENE-2899 > Project: Lucene - Core > Issue Type: New Feature > Components: modules/analysis >Reporter: Grant Ingersoll >Assignee: Grant Ingersoll >Priority: Minor > Attachments: LUCENE-2899.patch, LUCENE-2899.patch, LUCENE-2899.patch, > LUCENE-2899.patch, LUCENE-2899.patch, LUCENE-2899.patch, OpenNLPFilter.java, > OpenNLPTokenizer.java, opennlp_trunk.patch > > > Now that OpenNLP is an ASF project and has a nice license, it would be nice > to have a submodule (under analysis) that exposed capabilities for it. Drew > Farris, Tom Morton and I have code that does: > * Sentence Detection as a Tokenizer (could also be a TokenFilter, although it > would have to change slightly to buffer tokens) > * NamedEntity recognition as a TokenFilter > We are also planning a Tokenizer/TokenFilter that can put parts of speech as > either payloads (PartOfSpeechAttribute?) on a token or at the same position. > I'd propose it go under: > modules/analysis/opennlp -- 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 - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-1604) Wildcards, ORs etc inside Phrase Queries
[ https://issues.apache.org/jira/browse/SOLR-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438180#comment-13438180 ] Phani Vempaty commented on SOLR-1604: - Hello all, Could I get the grammar file (.jj file) for ComplexPhrase one - It's not there as part of the patch/zip file. Thanks, Phani. > Wildcards, ORs etc inside Phrase Queries > > > Key: SOLR-1604 > URL: https://issues.apache.org/jira/browse/SOLR-1604 > Project: Solr > Issue Type: Improvement > Components: search >Affects Versions: 1.4 >Reporter: Ahmet Arslan >Priority: Minor > Fix For: 4.0 > > Attachments: ComplexPhraseQueryParser.java, ComplexPhrase.zip, > ComplexPhrase.zip, ComplexPhrase.zip, ComplexPhrase.zip, ComplexPhrase.zip, > SOLR-1604-alternative.patch, SOLR-1604.patch, SOLR-1604.patch > > > Solr Plugin for ComplexPhraseQueryParser (LUCENE-1486) which supports > wildcards, ORs, ranges, fuzzies inside phrase queries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-3681) Index Version incompatibility between DirectoryReader and CommitPoint
[ https://issues.apache.org/jira/browse/SOLR-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phani Vempaty updated SOLR-3681: Attachment: replication_handler.patch A possible patch to get the Replication Handler working. > Index Version incompatibility between DirectoryReader and CommitPoint > - > > Key: SOLR-3681 > URL: https://issues.apache.org/jira/browse/SOLR-3681 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 4.0 > Environment: MAC OSX Darwin >Reporter: Phani Vempaty >Priority: Critical > Fix For: 4.0 > > Attachments: replication_handler.patch > > > There is incompatibility between Index version from Admin core & from the > response of a particular index url > For example:, > http://master_host/solr/core_name/replication?command=indexversion ... always > shows 0 as index version whereas the version in admin shows other version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3681) Index Version incompatibility between DirectoryReader and CommitPoint
[ https://issues.apache.org/jira/browse/SOLR-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423462#comment-13423462 ] Phani Vempaty commented on SOLR-3681: - I think it is a bug & I couldn't find similar bugs after searching and hence logging it .. if it is not please let me know. > Index Version incompatibility between DirectoryReader and CommitPoint > - > > Key: SOLR-3681 > URL: https://issues.apache.org/jira/browse/SOLR-3681 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 4.0 > Environment: MAC OSX Darwin >Reporter: Phani Vempaty >Priority: Critical > Fix For: 4.0 > > > There is incompatibility between Index version from Admin core & from the > response of a particular index url > For example:, > http://master_host/solr/core_name/replication?command=indexversion ... always > shows 0 as index version whereas the version in admin shows other version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-3681) Index Version incompatibility between DirectoryReader and CommitPoint
[ https://issues.apache.org/jira/browse/SOLR-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phani Vempaty updated SOLR-3681: Comment: was deleted (was: I think it is a bug .. if it is not please let me know .. I apologize for any inconvenience.) > Index Version incompatibility between DirectoryReader and CommitPoint > - > > Key: SOLR-3681 > URL: https://issues.apache.org/jira/browse/SOLR-3681 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 4.0 > Environment: MAC OSX Darwin >Reporter: Phani Vempaty >Priority: Critical > Fix For: 4.0 > > > There is incompatibility between Index version from Admin core & from the > response of a particular index url > For example:, > http://master_host/solr/core_name/replication?command=indexversion ... always > shows 0 as index version whereas the version in admin shows other version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3681) Index Version incompatibility between DirectoryReader and CommitPoint
[ https://issues.apache.org/jira/browse/SOLR-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423422#comment-13423422 ] Phani Vempaty commented on SOLR-3681: - I think it is a bug .. if it is not please let me know .. I apologize for any inconvenience. > Index Version incompatibility between DirectoryReader and CommitPoint > - > > Key: SOLR-3681 > URL: https://issues.apache.org/jira/browse/SOLR-3681 > Project: Solr > Issue Type: Bug > Components: replication (java) >Affects Versions: 4.0 > Environment: MAC OSX Darwin >Reporter: Phani Vempaty >Priority: Critical > Fix For: 4.0 > > > There is incompatibility between Index version from Admin core & from the > response of a particular index url > For example:, > http://master_host/solr/core_name/replication?command=indexversion ... always > shows 0 as index version whereas the version in admin shows other version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3681) Index Version incompatibility between DirectoryReader and CommitPoint
[
https://issues.apache.org/jira/browse/SOLR-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423420#comment-13423420
]
Phani Vempaty commented on SOLR-3681:
-
The Replication Handler response for the Index Version is based as ::
{code}
// always returns 0 as index version
rsp.add(CMD_INDEX_VERSION,
IndexDeletionPolicyWrapper.getCommitTimestamp(commitPoint));
{code}
{code}
// This returns another version number which is same as the one for admin core
Directory directory = commitPoint.getDirectory();
DirectoryReader directoryReader = DirectoryReader.open(directory);
rsp.add(CMD_INDEX_VERSION, directoryReader.getVersion());
{code}
> Index Version incompatibility between DirectoryReader and CommitPoint
> -
>
> Key: SOLR-3681
> URL: https://issues.apache.org/jira/browse/SOLR-3681
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
>Affects Versions: 4.0
> Environment: MAC OSX Darwin
>Reporter: Phani Vempaty
>Priority: Critical
> Fix For: 4.0
>
>
> There is incompatibility between Index version from Admin core & from the
> response of a particular index url
> For example:,
> http://master_host/solr/core_name/replication?command=indexversion ... always
> shows 0 as index version whereas the version in admin shows other version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3681) Index Version incompatibility between DirectoryReader and CommitPoint
Phani Vempaty created SOLR-3681: --- Summary: Index Version incompatibility between DirectoryReader and CommitPoint Key: SOLR-3681 URL: https://issues.apache.org/jira/browse/SOLR-3681 Project: Solr Issue Type: Bug Components: replication (java) Affects Versions: 4.0 Environment: MAC OSX Darwin Reporter: Phani Vempaty Priority: Critical Fix For: 4.0 There is incompatibility between Index version from Admin core & from the response of a particular index url For example:, http://master_host/solr/core_name/replication?command=indexversion ... always shows 0 as index version whereas the version in admin shows other version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3651) unable to find Instance directory names with "."
[ https://issues.apache.org/jira/browse/SOLR-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418761#comment-13418761 ] Phani Vempaty commented on SOLR-3651: - Hello Hoss, Yes, that is correct. I'm not able to see anything in solr logs - no exceptions nothing. even, when I try to load it directly, it says "404 Not Found #/vempap.public.message" I tried debugging how the request is passing - for some means proper path is not being sent to the "SolrDispatchFilter" (the request path is just /) .. but when I change "." with "_", then it gets the correct path. > unable to find Instance directory names with "." > > > Key: SOLR-3651 > URL: https://issues.apache.org/jira/browse/SOLR-3651 > Project: Solr > Issue Type: Bug > Components: multicore >Affects Versions: 4.0-ALPHA > Environment: MacOSX Darwin >Reporter: Phani Vempaty > Labels: patch > > In multicore scenario, if I have "." in instance directory name - it is not > able to find it in solr UI or even not able to ping it due to which I'm not > able to get the statistics regarding that particular index like last modified > time etc.. > Example: > Try giving an instance directory name as "vempap.public.message" - you can > see the core loaded in the UI, but when you click on it - it says > "vempap.public.message" Not Found .. I spent a lot of time debugging & now, > when I just replace "." with "_" - it works fine & well.. > Please let me know if it is intended to be like that or it is a bug. Sorry it > is already mentioned earlier - couldn't find related bug when I did a quick > search. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-3651) unable to find Instance directory names with "."
Phani Vempaty created SOLR-3651: --- Summary: unable to find Instance directory names with "." Key: SOLR-3651 URL: https://issues.apache.org/jira/browse/SOLR-3651 Project: Solr Issue Type: Bug Components: multicore Affects Versions: 4.0-ALPHA Environment: MacOSX Darwin Reporter: Phani Vempaty In multicore scenario, if I have "." in instance directory name - it is not able to find it in solr UI or even not able to ping it due to which I'm not able to get the statistics regarding that particular index like last modified time etc.. Example: Try giving an instance directory name as "vempap.public.message" - you can see the core loaded in the UI, but when you click on it - it says "vempap.public.message" Not Found .. I spent a lot of time debugging & now, when I just replace "." with "_" - it works fine & well.. Please let me know if it is intended to be like that or it is a bug. Sorry it is already mentioned earlier - couldn't find related bug when I did a quick search. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
