[jira] [Commented] (SOLR-12663) Highlighting is not working with docValues only String fiel
[ https://issues.apache.org/jira/browse/SOLR-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582988#comment-16582988 ] Karthik Ramachandran commented on SOLR-12663: - I think it would be better to make changes once [SOLR-12625|https://issues.apache.org/jira/browse/SOLR-12625] has been committed > Highlighting is not working with docValues only String fiel > --- > > Key: SOLR-12663 > URL: https://issues.apache.org/jira/browse/SOLR-12663 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: highlighter >Affects Versions: 7.2.1 >Reporter: Karthik Ramachandran >Priority: Major > > Highlighting is not working with docValues only String field. Need to check > SortableTextField as mentioned by [~erickerickson] > Schema: > > id > > required="true"/> > stored="true"/> > stored="false"/> > > > Data: > [\\{"id":1,"name":"Testing line 1"},\\{"id":2,"name":"Testing line > 2"},\\{"id":3,"name":"Testing line 3"}] > Query: > > [http://localhost:8983/solr/test/select?q=Testing*&df=name&hl=true&hl.fl=name,name1] > Response: > {"response":{"numFound":3,"start":0,"docs":[ > {"id":"1","name":"Testing line 1","name1":"Testing line 1"} > ,\{"id":"2","name":"Testing line 2","name1":"Testing line > 2"},\{"id":"3","name":"Testing line 3","name1":"Testing line > 3"}]},"highlighting":{"1": > {"name":["Testing line 1"]} > ,"2":{"name":["Testing line 2"]},"3":{"name":["Testing line > 3"]}}} -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-12663) Highlighting is not working with docValues only String field
[ https://issues.apache.org/jira/browse/SOLR-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-12663: Summary: Highlighting is not working with docValues only String field (was: Highlighting is not working with docValues only String fiel) > Highlighting is not working with docValues only String field > > > Key: SOLR-12663 > URL: https://issues.apache.org/jira/browse/SOLR-12663 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: highlighter >Affects Versions: 7.2.1 >Reporter: Karthik Ramachandran >Priority: Major > > Highlighting is not working with docValues only String field. Need to check > SortableTextField as mentioned by [~erickerickson] > Schema: > > id > > required="true"/> > stored="true"/> > stored="false"/> > > > Data: > [\\{"id":1,"name":"Testing line 1"},\\{"id":2,"name":"Testing line > 2"},\\{"id":3,"name":"Testing line 3"}] > Query: > > [http://localhost:8983/solr/test/select?q=Testing*&df=name&hl=true&hl.fl=name,name1] > Response: > {"response":{"numFound":3,"start":0,"docs":[ > {"id":"1","name":"Testing line 1","name1":"Testing line 1"} > ,\{"id":"2","name":"Testing line 2","name1":"Testing line > 2"},\{"id":"3","name":"Testing line 3","name1":"Testing line > 3"}]},"highlighting":{"1": > {"name":["Testing line 1"]} > ,"2":{"name":["Testing line 2"]},"3":{"name":["Testing line > 3"]}}} -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-12663) Highlighting is not working with docValues only String fiel
Karthik Ramachandran created SOLR-12663: --- Summary: Highlighting is not working with docValues only String fiel Key: SOLR-12663 URL: https://issues.apache.org/jira/browse/SOLR-12663 Project: Solr Issue Type: Bug Security Level: Public (Default Security Level. Issues are Public) Components: highlighter Affects Versions: 7.2.1 Reporter: Karthik Ramachandran Highlighting is not working with docValues only String field. Schema: id Data: [\{"id":1,"name":"Testing line 1"},\{"id":2,"name":"Testing line 2"},\{"id":3,"name":"Testing line 3"}] Query: [http://localhost:8983/solr/test/select?q=Testing*&df=name&hl=true&hl.fl=name,name1] Response: {"response":\{"numFound":3,"start":0,"docs":[{"id":"1","name":"Testing line 1","name1":"Testing line 1"},\{"id":"2","name":"Testing line 2","name1":"Testing line 2"},\{"id":"3","name":"Testing line 3","name1":"Testing line 3"}]},"highlighting":\{"1":{"name":["Testing line 1"]},"2":\{"name":["Testing line 2"]},"3":\{"name":["Testing line 3"]}}} -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-12663) Highlighting is not working with docValues only String fiel
[ https://issues.apache.org/jira/browse/SOLR-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-12663: Description: Highlighting is not working with docValues only String field. Need to check SortableTextField as mentioned by [~erickerickson] Schema: id Data: [\\{"id":1,"name":"Testing line 1"},\\{"id":2,"name":"Testing line 2"},\\{"id":3,"name":"Testing line 3"}] Query: [http://localhost:8983/solr/test/select?q=Testing*&df=name&hl=true&hl.fl=name,name1] Response: {"response":{"numFound":3,"start":0,"docs":[ {"id":"1","name":"Testing line 1","name1":"Testing line 1"} ,\{"id":"2","name":"Testing line 2","name1":"Testing line 2"},\{"id":"3","name":"Testing line 3","name1":"Testing line 3"}]},"highlighting":{"1": {"name":["Testing line 1"]} ,"2":{"name":["Testing line 2"]},"3":{"name":["Testing line 3"]}}} was: Highlighting is not working with docValues only String field. Schema: id Data: [\{"id":1,"name":"Testing line 1"},\{"id":2,"name":"Testing line 2"},\{"id":3,"name":"Testing line 3"}] Query: [http://localhost:8983/solr/test/select?q=Testing*&df=name&hl=true&hl.fl=name,name1] Response: {"response":\{"numFound":3,"start":0,"docs":[{"id":"1","name":"Testing line 1","name1":"Testing line 1"},\{"id":"2","name":"Testing line 2","name1":"Testing line 2"},\{"id":"3","name":"Testing line 3","name1":"Testing line 3"}]},"highlighting":\{"1":{"name":["Testing line 1"]},"2":\{"name":["Testing line 2"]},"3":\{"name":["Testing line 3"]}}} > Highlighting is not working with docValues only String fiel > --- > > Key: SOLR-12663 > URL: https://issues.apache.org/jira/browse/SOLR-12663 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: highlighter >Affects Versions: 7.2.1 >Reporter: Karthik Ramachandran >Priority: Major > > Highlighting is not working with docValues only String field. Need to check > SortableTextField as mentioned by [~erickerickson] > Schema: > > id > > required="true"/> > stored="true"/> > stored="false"/> > > > Data: > [\\{"id":1,"name":"Testing line 1"},\\{"id":2,"name":"Testing line > 2"},\\{"id":3,"name":"Testing line 3"}] > Query: > > [http://localhost:8983/solr/test/select?q=Testing*&df=name&hl=true&hl.fl=name,name1] > Response: > {"response":{"numFound":3,"start":0,"docs":[ > {"id":"1","name":"Testing line 1","name1":"Testing line 1"} > ,\{"id":"2","name":"Testing line 2","name1":"Testing line > 2"},\{"id":"3","name":"Testing line 3","name1":"Testing line > 3"}]},"highlighting":{"1": > {"name":["Testing line 1"]} > ,"2":{"name":["Testing line 2"]},"3":{"name":["Testing line > 3"]}}} -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11731) LatLonPointSpatialField could be improved to return the lat/lon from docValues
[ https://issues.apache.org/jira/browse/SOLR-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403114#comment-16403114 ] Karthik Ramachandran commented on SOLR-11731: - Looks good to me. [~dsmiley] Thanks for making changes to test. > LatLonPointSpatialField could be improved to return the lat/lon from docValues > -- > > Key: SOLR-11731 > URL: https://issues.apache.org/jira/browse/SOLR-11731 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: spatial >Reporter: David Smiley >Assignee: David Smiley >Priority: Minor > Attachments: SOLR-11731.patch, SOLR-11731.patch, SOLR-11731.patch > > Time Spent: 4h 20m > Remaining Estimate: 0h > > You can only return the lat & lon from a LatLonPointSpatialField if you set > stored=true. But we could allow this (albeit at a small loss in precision) > if stored=false and docValues=true. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-12064) NullPointerException in JSON facet
Karthik Ramachandran created SOLR-12064: --- Summary: NullPointerException in JSON facet Key: SOLR-12064 URL: https://issues.apache.org/jira/browse/SOLR-12064 Project: Solr Issue Type: Improvement Security Level: Public (Default Security Level. Issues are Public) Components: Facet Module Affects Versions: 7.2 Reporter: Karthik Ramachandran NullPointerException in JSON facet when using terms with limit -1 and more than one facet {f1:{terms:{field:'cat_ldS', limit:-1, sort:'n1 desc', facet:{n1:'avg(num_ldS)', n2:'sum(num_ldS)'} {noformat} java.lang.NullPointerException at org.apache.solr.search.facet.AvgSlotAcc.collect(SlotAcc.java:390) at org.apache.solr.search.facet.FacetFieldProcessor$MultiAcc.collect(FacetFieldProcessor.java:510) at org.apache.solr.search.facet.SlotAcc.collect(SlotAcc.java:97) at org.apache.solr.search.facet.FacetFieldProcessor.collectFirstPhase(FacetFieldProcessor.java:220) at org.apache.solr.search.facet.UnInvertedField.collectDocsGeneric(UnInvertedField.java:431) at org.apache.solr.search.facet.UnInvertedField.collectDocs(UnInvertedField.java:410) at org.apache.solr.search.facet.FacetFieldProcessorByArrayUIF.collectDocs(FacetFieldProcessorByArrayUIF.java:64) at org.apache.solr.search.facet.FacetFieldProcessorByArray.calcFacets(FacetFieldProcessorByArray.java:108) at org.apache.solr.search.facet.FacetFieldProcessorByArray.process(FacetFieldProcessorByArray.java:58) at org.apache.solr.search.facet.FacetProcessor.processSubs(FacetProcessor.java:460) at org.apache.solr.search.facet.FacetProcessor.fillBucket(FacetProcessor.java:407) at org.apache.solr.search.facet.FacetQueryProcessor.process(FacetQuery.java:64) at org.apache.solr.search.facet.FacetModule.process(FacetModule.java:154) at org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:295) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:180) at org.apache.solr.core.SolrCore.execute(SolrCore.java:2503) at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:710) at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:516) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12064) NullPointerException in JSON facet
[ https://issues.apache.org/jira/browse/SOLR-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390134#comment-16390134 ] Karthik Ramachandran commented on SOLR-12064: - I see an issue in TestJsonFacets class. After fixing the test case finding more issue with missing:true and limit-1 [^patch.diff] > NullPointerException in JSON facet > -- > > Key: SOLR-12064 > URL: https://issues.apache.org/jira/browse/SOLR-12064 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: Facet Module >Affects Versions: 7.2 >Reporter: Karthik Ramachandran >Priority: Major > Attachments: patch.diff > > > NullPointerException in JSON facet when using terms with limit -1 and more > than one facet > {f1:{terms:{field:'cat_ldS', limit:-1, sort:'n1 desc', > facet:{n1:'avg(num_ldS)', n2:'sum(num_ldS)'} > {noformat} > java.lang.NullPointerException > at org.apache.solr.search.facet.AvgSlotAcc.collect(SlotAcc.java:390) > at > org.apache.solr.search.facet.FacetFieldProcessor$MultiAcc.collect(FacetFieldProcessor.java:510) > at org.apache.solr.search.facet.SlotAcc.collect(SlotAcc.java:97) > at > org.apache.solr.search.facet.FacetFieldProcessor.collectFirstPhase(FacetFieldProcessor.java:220) > at > org.apache.solr.search.facet.UnInvertedField.collectDocsGeneric(UnInvertedField.java:431) > at > org.apache.solr.search.facet.UnInvertedField.collectDocs(UnInvertedField.java:410) > at > org.apache.solr.search.facet.FacetFieldProcessorByArrayUIF.collectDocs(FacetFieldProcessorByArrayUIF.java:64) > at > org.apache.solr.search.facet.FacetFieldProcessorByArray.calcFacets(FacetFieldProcessorByArray.java:108) > at > org.apache.solr.search.facet.FacetFieldProcessorByArray.process(FacetFieldProcessorByArray.java:58) > at > org.apache.solr.search.facet.FacetProcessor.processSubs(FacetProcessor.java:460) > at > org.apache.solr.search.facet.FacetProcessor.fillBucket(FacetProcessor.java:407) > at > org.apache.solr.search.facet.FacetQueryProcessor.process(FacetQuery.java:64) > at org.apache.solr.search.facet.FacetModule.process(FacetModule.java:154) > at > org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:295) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:180) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2503) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:710) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:516) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-12064) NullPointerException in JSON facet
[ https://issues.apache.org/jira/browse/SOLR-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-12064: Attachment: patch.diff > NullPointerException in JSON facet > -- > > Key: SOLR-12064 > URL: https://issues.apache.org/jira/browse/SOLR-12064 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: Facet Module >Affects Versions: 7.2 >Reporter: Karthik Ramachandran >Priority: Major > Attachments: patch.diff > > > NullPointerException in JSON facet when using terms with limit -1 and more > than one facet > {f1:{terms:{field:'cat_ldS', limit:-1, sort:'n1 desc', > facet:{n1:'avg(num_ldS)', n2:'sum(num_ldS)'} > {noformat} > java.lang.NullPointerException > at org.apache.solr.search.facet.AvgSlotAcc.collect(SlotAcc.java:390) > at > org.apache.solr.search.facet.FacetFieldProcessor$MultiAcc.collect(FacetFieldProcessor.java:510) > at org.apache.solr.search.facet.SlotAcc.collect(SlotAcc.java:97) > at > org.apache.solr.search.facet.FacetFieldProcessor.collectFirstPhase(FacetFieldProcessor.java:220) > at > org.apache.solr.search.facet.UnInvertedField.collectDocsGeneric(UnInvertedField.java:431) > at > org.apache.solr.search.facet.UnInvertedField.collectDocs(UnInvertedField.java:410) > at > org.apache.solr.search.facet.FacetFieldProcessorByArrayUIF.collectDocs(FacetFieldProcessorByArrayUIF.java:64) > at > org.apache.solr.search.facet.FacetFieldProcessorByArray.calcFacets(FacetFieldProcessorByArray.java:108) > at > org.apache.solr.search.facet.FacetFieldProcessorByArray.process(FacetFieldProcessorByArray.java:58) > at > org.apache.solr.search.facet.FacetProcessor.processSubs(FacetProcessor.java:460) > at > org.apache.solr.search.facet.FacetProcessor.fillBucket(FacetProcessor.java:407) > at > org.apache.solr.search.facet.FacetQueryProcessor.process(FacetQuery.java:64) > at org.apache.solr.search.facet.FacetModule.process(FacetModule.java:154) > at > org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:295) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:180) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2503) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:710) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:516) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12064) NullPointerException in JSON facet
[ https://issues.apache.org/jira/browse/SOLR-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390478#comment-16390478 ] Karthik Ramachandran commented on SOLR-12064: - Adding one more testcase which need fixes for multiple facet [^patch.diff] > NullPointerException in JSON facet > -- > > Key: SOLR-12064 > URL: https://issues.apache.org/jira/browse/SOLR-12064 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Facet Module >Affects Versions: 7.2 >Reporter: Karthik Ramachandran >Assignee: Yonik Seeley >Priority: Major > Attachments: patch.diff, patch.diff > > > NullPointerException in JSON facet when using terms with limit -1 and more > than one facet > {f1:{terms:{field:'cat_ldS', limit:-1, sort:'n1 desc', > facet:{n1:'avg(num_ldS)', n2:'sum(num_ldS)'} > {noformat} > java.lang.NullPointerException > at org.apache.solr.search.facet.AvgSlotAcc.collect(SlotAcc.java:390) > at > org.apache.solr.search.facet.FacetFieldProcessor$MultiAcc.collect(FacetFieldProcessor.java:510) > at org.apache.solr.search.facet.SlotAcc.collect(SlotAcc.java:97) > at > org.apache.solr.search.facet.FacetFieldProcessor.collectFirstPhase(FacetFieldProcessor.java:220) > at > org.apache.solr.search.facet.UnInvertedField.collectDocsGeneric(UnInvertedField.java:431) > at > org.apache.solr.search.facet.UnInvertedField.collectDocs(UnInvertedField.java:410) > at > org.apache.solr.search.facet.FacetFieldProcessorByArrayUIF.collectDocs(FacetFieldProcessorByArrayUIF.java:64) > at > org.apache.solr.search.facet.FacetFieldProcessorByArray.calcFacets(FacetFieldProcessorByArray.java:108) > at > org.apache.solr.search.facet.FacetFieldProcessorByArray.process(FacetFieldProcessorByArray.java:58) > at > org.apache.solr.search.facet.FacetProcessor.processSubs(FacetProcessor.java:460) > at > org.apache.solr.search.facet.FacetProcessor.fillBucket(FacetProcessor.java:407) > at > org.apache.solr.search.facet.FacetQueryProcessor.process(FacetQuery.java:64) > at org.apache.solr.search.facet.FacetModule.process(FacetModule.java:154) > at > org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:295) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:180) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2503) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:710) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:516) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-12064) NullPointerException in JSON facet
[ https://issues.apache.org/jira/browse/SOLR-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-12064: Attachment: patch.diff > NullPointerException in JSON facet > -- > > Key: SOLR-12064 > URL: https://issues.apache.org/jira/browse/SOLR-12064 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Facet Module >Affects Versions: 7.2 >Reporter: Karthik Ramachandran >Assignee: Yonik Seeley >Priority: Major > Attachments: patch.diff, patch.diff > > > NullPointerException in JSON facet when using terms with limit -1 and more > than one facet > {f1:{terms:{field:'cat_ldS', limit:-1, sort:'n1 desc', > facet:{n1:'avg(num_ldS)', n2:'sum(num_ldS)'} > {noformat} > java.lang.NullPointerException > at org.apache.solr.search.facet.AvgSlotAcc.collect(SlotAcc.java:390) > at > org.apache.solr.search.facet.FacetFieldProcessor$MultiAcc.collect(FacetFieldProcessor.java:510) > at org.apache.solr.search.facet.SlotAcc.collect(SlotAcc.java:97) > at > org.apache.solr.search.facet.FacetFieldProcessor.collectFirstPhase(FacetFieldProcessor.java:220) > at > org.apache.solr.search.facet.UnInvertedField.collectDocsGeneric(UnInvertedField.java:431) > at > org.apache.solr.search.facet.UnInvertedField.collectDocs(UnInvertedField.java:410) > at > org.apache.solr.search.facet.FacetFieldProcessorByArrayUIF.collectDocs(FacetFieldProcessorByArrayUIF.java:64) > at > org.apache.solr.search.facet.FacetFieldProcessorByArray.calcFacets(FacetFieldProcessorByArray.java:108) > at > org.apache.solr.search.facet.FacetFieldProcessorByArray.process(FacetFieldProcessorByArray.java:58) > at > org.apache.solr.search.facet.FacetProcessor.processSubs(FacetProcessor.java:460) > at > org.apache.solr.search.facet.FacetProcessor.fillBucket(FacetProcessor.java:407) > at > org.apache.solr.search.facet.FacetQueryProcessor.process(FacetQuery.java:64) > at org.apache.solr.search.facet.FacetModule.process(FacetModule.java:154) > at > org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:295) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:180) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2503) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:710) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:516) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-12064) NullPointerException in JSON facet
[ https://issues.apache.org/jira/browse/SOLR-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-12064: Attachment: SOLR-12064.patch > NullPointerException in JSON facet > -- > > Key: SOLR-12064 > URL: https://issues.apache.org/jira/browse/SOLR-12064 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Facet Module >Affects Versions: 7.2 >Reporter: Karthik Ramachandran >Assignee: Yonik Seeley >Priority: Major > Attachments: SOLR-12064.patch, patch.diff, patch.diff > > Time Spent: 10m > Remaining Estimate: 0h > > NullPointerException in JSON facet when using terms with limit -1 and more > than one facet > {f1:{terms:{field:'cat_ldS', limit:-1, sort:'n1 desc', > facet:{n1:'avg(num_ldS)', n2:'sum(num_ldS)'} > {noformat} > java.lang.NullPointerException > at org.apache.solr.search.facet.AvgSlotAcc.collect(SlotAcc.java:390) > at > org.apache.solr.search.facet.FacetFieldProcessor$MultiAcc.collect(FacetFieldProcessor.java:510) > at org.apache.solr.search.facet.SlotAcc.collect(SlotAcc.java:97) > at > org.apache.solr.search.facet.FacetFieldProcessor.collectFirstPhase(FacetFieldProcessor.java:220) > at > org.apache.solr.search.facet.UnInvertedField.collectDocsGeneric(UnInvertedField.java:431) > at > org.apache.solr.search.facet.UnInvertedField.collectDocs(UnInvertedField.java:410) > at > org.apache.solr.search.facet.FacetFieldProcessorByArrayUIF.collectDocs(FacetFieldProcessorByArrayUIF.java:64) > at > org.apache.solr.search.facet.FacetFieldProcessorByArray.calcFacets(FacetFieldProcessorByArray.java:108) > at > org.apache.solr.search.facet.FacetFieldProcessorByArray.process(FacetFieldProcessorByArray.java:58) > at > org.apache.solr.search.facet.FacetProcessor.processSubs(FacetProcessor.java:460) > at > org.apache.solr.search.facet.FacetProcessor.fillBucket(FacetProcessor.java:407) > at > org.apache.solr.search.facet.FacetQueryProcessor.process(FacetQuery.java:64) > at org.apache.solr.search.facet.FacetModule.process(FacetModule.java:154) > at > org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:295) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:180) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2503) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:710) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:516) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12064) NullPointerException in JSON facet
[ https://issues.apache.org/jira/browse/SOLR-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390533#comment-16390533 ] Karthik Ramachandran commented on SOLR-12064: - [~ysee...@gmail.com] i have attempted to fix the issue, can you please review the change? > NullPointerException in JSON facet > -- > > Key: SOLR-12064 > URL: https://issues.apache.org/jira/browse/SOLR-12064 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Facet Module >Affects Versions: 7.2 >Reporter: Karthik Ramachandran >Assignee: Yonik Seeley >Priority: Major > Attachments: SOLR-12064.patch, patch.diff, patch.diff > > Time Spent: 10m > Remaining Estimate: 0h > > NullPointerException in JSON facet when using terms with limit -1 and more > than one facet > {f1:{terms:{field:'cat_ldS', limit:-1, sort:'n1 desc', > facet:{n1:'avg(num_ldS)', n2:'sum(num_ldS)'} > {noformat} > java.lang.NullPointerException > at org.apache.solr.search.facet.AvgSlotAcc.collect(SlotAcc.java:390) > at > org.apache.solr.search.facet.FacetFieldProcessor$MultiAcc.collect(FacetFieldProcessor.java:510) > at org.apache.solr.search.facet.SlotAcc.collect(SlotAcc.java:97) > at > org.apache.solr.search.facet.FacetFieldProcessor.collectFirstPhase(FacetFieldProcessor.java:220) > at > org.apache.solr.search.facet.UnInvertedField.collectDocsGeneric(UnInvertedField.java:431) > at > org.apache.solr.search.facet.UnInvertedField.collectDocs(UnInvertedField.java:410) > at > org.apache.solr.search.facet.FacetFieldProcessorByArrayUIF.collectDocs(FacetFieldProcessorByArrayUIF.java:64) > at > org.apache.solr.search.facet.FacetFieldProcessorByArray.calcFacets(FacetFieldProcessorByArray.java:108) > at > org.apache.solr.search.facet.FacetFieldProcessorByArray.process(FacetFieldProcessorByArray.java:58) > at > org.apache.solr.search.facet.FacetProcessor.processSubs(FacetProcessor.java:460) > at > org.apache.solr.search.facet.FacetProcessor.fillBucket(FacetProcessor.java:407) > at > org.apache.solr.search.facet.FacetQueryProcessor.process(FacetQuery.java:64) > at org.apache.solr.search.facet.FacetModule.process(FacetModule.java:154) > at > org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:295) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:180) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2503) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:710) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:516) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-11731) LatLonPointSpatialField could be improved to return the lat/lon from docValues
[ https://issues.apache.org/jira/browse/SOLR-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11731: Attachment: SOLR-11731.patch > LatLonPointSpatialField could be improved to return the lat/lon from docValues > -- > > Key: SOLR-11731 > URL: https://issues.apache.org/jira/browse/SOLR-11731 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: spatial >Reporter: David Smiley >Priority: Minor > Attachments: SOLR-11731.patch, SOLR-11731.patch > > Time Spent: 2h 10m > Remaining Estimate: 0h > > You can only return the lat & lon from a LatLonPointSpatialField if you set > stored=true. But we could allow this (albeit at a small loss in precision) > if stored=false and docValues=true. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-11331) Ability to Debug Solr With Eclipse IDE
[ https://issues.apache.org/jira/browse/SOLR-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11331: Attachment: SOLR-11331.diff > Ability to Debug Solr With Eclipse IDE > -- > > Key: SOLR-11331 > URL: https://issues.apache.org/jira/browse/SOLR-11331 > Project: Solr > Issue Type: Improvement >Affects Versions: 6.6.2 >Reporter: Karthik Ramachandran >Priority: Minor > Labels: eclipse > Attachments: SOLR-11331.diff, SOLR-11331.patch, SOLR-11331.patch, > UI.png > > > Ability to Debug Solr With Eclipse IDE -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11331) Ability to Debug Solr With Eclipse IDE
[ https://issues.apache.org/jira/browse/SOLR-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396480#comment-16396480 ] Karthik Ramachandran commented on SOLR-11331: - I had removed a macro that was applied during build. I have updated the PR and patch. > Ability to Debug Solr With Eclipse IDE > -- > > Key: SOLR-11331 > URL: https://issues.apache.org/jira/browse/SOLR-11331 > Project: Solr > Issue Type: Improvement >Affects Versions: 6.6.2 >Reporter: Karthik Ramachandran >Priority: Minor > Labels: eclipse > Attachments: SOLR-11331.diff, SOLR-11331.patch, SOLR-11331.patch, > UI.png > > > Ability to Debug Solr With Eclipse IDE -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7495) Unexpected docvalues type NUMERIC when grouping by a int facet
[ https://issues.apache.org/jira/browse/SOLR-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229414#comment-15229414 ] Karthik Ramachandran commented on SOLR-7495: Having the same issue in 5.5, will this be fixed any time soon? > Unexpected docvalues type NUMERIC when grouping by a int facet > -- > > Key: SOLR-7495 > URL: https://issues.apache.org/jira/browse/SOLR-7495 > Project: Solr > Issue Type: Bug >Affects Versions: 5.0, 5.1, 5.2, 5.3 >Reporter: Fabio Batista da Silva > Attachments: SOLR-7495.patch > > > Hey All, > After upgrading from solr 4.10 to 5.1 with solr could > I'm getting a IllegalStateException when i try to facet a int field. > IllegalStateException: unexpected docvalues type NUMERIC for field 'year' > (expected=SORTED). Use UninvertingReader or index with docvalues. > schema.xml > {code} > > > > > > > multiValued="false" required="true"/> > multiValued="false" required="true"/> > > > stored="true"/> > > > > /> > sortMissingLast="true"/> > positionIncrementGap="0"/> > positionIncrementGap="0"/> > positionIncrementGap="0"/> > precisionStep="0" positionIncrementGap="0"/> > positionIncrementGap="0"/> > positionIncrementGap="100"> > > > words="stopwords.txt" /> > > maxGramSize="15"/> > > > > words="stopwords.txt" /> > synonyms="synonyms.txt" ignoreCase="true" expand="true"/> > > > > positionIncrementGap="100"> > > > words="stopwords.txt" /> > > maxGramSize="15"/> > > > > words="stopwords.txt" /> > synonyms="synonyms.txt" ignoreCase="true" expand="true"/> > > > > class="solr.SpatialRecursivePrefixTreeFieldType" geo="true" > distErrPct="0.025" maxDistErr="0.09" units="degrees" /> > > id > name > > > {code} > query : > {code} > http://solr.dev:8983/solr/my_collection/select?wt=json&fl=id&fq=index_type:foobar&group=true&group.field=year_make_model&group.facet=true&facet=true&facet.field=year > {code} > Exception : > {code} > ull:org.apache.solr.common.SolrException: Exception during facet.field: year > at org.apache.solr.request.SimpleFacets$3.call(SimpleFacets.java:627) > at org.apache.solr.request.SimpleFacets$3.call(SimpleFacets.java:612) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at org.apache.solr.request.SimpleFacets$2.execute(SimpleFacets.java:566) > at > org.apache.solr.request.SimpleFacets.getFacetFieldCounts(SimpleFacets.java:637) > at > org.apache.solr.request.SimpleFacets.getFacetCounts(SimpleFacets.java:280) > at > org.apache.solr.handler.component.FacetComponent.process(FacetComponent.java:106) > at > org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:222) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:1984) > at > org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:829) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:446) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:220) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(
[jira] [Created] (SOLR-9034) Atomic updates not work with CopyField
Karthik Ramachandran created SOLR-9034: -- Summary: Atomic updates not work with CopyField Key: SOLR-9034 URL: https://issues.apache.org/jira/browse/SOLR-9034 Project: Solr Issue Type: Bug Components: Server Affects Versions: 5.5 Reporter: Karthik Ramachandran Atomic updates does not work when CopyField has docValues enabled. Below is the sample schema {code:xml|title:schema.xml} {code} Below is the exception {noformat} Caused by: java.lang.IllegalArgumentException: DocValuesField "copy_single_i_dvn" appears more than once in this document (only one value is allowed per field) {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-9034) Atomic updates not work with CopyField
[ https://issues.apache.org/jira/browse/SOLR-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-9034: --- Attachment: SOLR-9034.patch > Atomic updates not work with CopyField > -- > > Key: SOLR-9034 > URL: https://issues.apache.org/jira/browse/SOLR-9034 > Project: Solr > Issue Type: Bug > Components: Server >Affects Versions: 5.5 >Reporter: Karthik Ramachandran > Labels: atomicupdate > Attachments: SOLR-9034.patch > > > Atomic updates does not work when CopyField has docValues enabled. Below is > the sample schema > {code:xml|title:schema.xml} > indexed="true" stored="true" /> > indexed="true" stored="true" /> > indexed="true" stored="true" /> > docValues="true" indexed="true" stored="false" useDocValuesAsStored="false" /> > docValues="true" indexed="true" stored="false" useDocValuesAsStored="false" /> > docValues="true" indexed="true" stored="false" useDocValuesAsStored="false" /> > {code} > Below is the exception > {noformat} > Caused by: java.lang.IllegalArgumentException: DocValuesField > "copy_single_i_dvn" appears more than once in this document > (only one value is allowed per field) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9034) Atomic updates not work with CopyField
[ https://issues.apache.org/jira/browse/SOLR-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255762#comment-15255762 ] Karthik Ramachandran commented on SOLR-9034: Can someone review the change? It would good if this fix makes it to 5.5.1 > Atomic updates not work with CopyField > -- > > Key: SOLR-9034 > URL: https://issues.apache.org/jira/browse/SOLR-9034 > Project: Solr > Issue Type: Bug > Components: Server >Affects Versions: 5.5 >Reporter: Karthik Ramachandran > Labels: atomicupdate > Attachments: SOLR-9034.patch > > > Atomic updates does not work when CopyField has docValues enabled. Below is > the sample schema > {code:xml|title:schema.xml} > indexed="true" stored="true" /> > indexed="true" stored="true" /> > indexed="true" stored="true" /> > docValues="true" indexed="true" stored="false" useDocValuesAsStored="false" /> > docValues="true" indexed="true" stored="false" useDocValuesAsStored="false" /> > docValues="true" indexed="true" stored="false" useDocValuesAsStored="false" /> > {code} > Below is the exception > {noformat} > Caused by: java.lang.IllegalArgumentException: DocValuesField > "copy_single_i_dvn" appears more than once in this document > (only one value is allowed per field) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9034) Atomic updates not work with CopyField
[ https://issues.apache.org/jira/browse/SOLR-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258825#comment-15258825 ] Karthik Ramachandran commented on SOLR-9034: Changes looks good. > Atomic updates not work with CopyField > -- > > Key: SOLR-9034 > URL: https://issues.apache.org/jira/browse/SOLR-9034 > Project: Solr > Issue Type: Bug > Components: Server >Affects Versions: 5.5 >Reporter: Karthik Ramachandran >Assignee: Yonik Seeley > Labels: atomicupdate > Attachments: SOLR-9034.patch, SOLR-9034.patch, SOLR-9034.patch > > > Atomic updates does not work when CopyField has docValues enabled. Below is > the sample schema > {code:xml|title:schema.xml} > indexed="true" stored="true" /> > indexed="true" stored="true" /> > indexed="true" stored="true" /> > docValues="true" indexed="true" stored="false" useDocValuesAsStored="false" /> > docValues="true" indexed="true" stored="false" useDocValuesAsStored="false" /> > docValues="true" indexed="true" stored="false" useDocValuesAsStored="false" /> > {code} > Below is the exception > {noformat} > Caused by: java.lang.IllegalArgumentException: DocValuesField > "copy_single_i_dvn" appears more than once in this document > (only one value is allowed per field) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-11304) Exception while returning document if LatLonPointSpatialField field is not stored
Karthik Ramachandran created SOLR-11304: --- Summary: Exception while returning document if LatLonPointSpatialField field is not stored Key: SOLR-11304 URL: https://issues.apache.org/jira/browse/SOLR-11304 Project: Solr Issue Type: Bug Security Level: Public (Default Security Level. Issues are Public) Affects Versions: 6.6, 7.0 Reporter: Karthik Ramachandran NullPointerException while retrieving the document if LatLonPointSpatialField is not stored {code:xml} {code} {code} 2017-08-31 12:18:23.368 ERROR (qtp1866850137-23) [ x:latlon] o.a.s.s.HttpSolrCall null:java.lang.NullPointerException at org.apache.solr.search.SolrDocumentFetcher.decorateDocValueFields(SolrDocumentFetcher.java:510) at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:160) at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:1) at org.apache.solr.response.TextResponseWriter.writeDocuments(TextResponseWriter.java:275) at org.apache.solr.response.TextResponseWriter.writeVal(TextResponseWriter.java:161) at org.apache.solr.response.JSONWriter.writeNamedListAsMapWithDups(JSONResponseWriter.java:209) at org.apache.solr.response.JSONWriter.writeNamedList(JSONResponseWriter.java:325) at org.apache.solr.response.JSONWriter.writeResponse(JSONResponseWriter.java:120) at org.apache.solr.response.JSONResponseWriter.write(JSONResponseWriter.java:71) at org.apache.solr.response.QueryResponseWriterUtil.writeQueryResponse(QueryResponseWriterUtil.java:65) at org.apache.solr.servlet.HttpSolrCall.writeResponse(HttpSolrCall.java:806) at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:535) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) at org.eclipse.jetty.server.Server.handle(Server.java:534) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) at java.lang.Thread.run(Unknown Source) {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-11190) GraphQuery not working if field has only docValues
Karthik Ramachandran created SOLR-11190: --- Summary: GraphQuery not working if field has only docValues Key: SOLR-11190 URL: https://issues.apache.org/jira/browse/SOLR-11190 Project: Solr Issue Type: Bug Security Level: Public (Default Security Level. Issues are Public) Components: query parsers Affects Versions: 6.6 Reporter: Karthik Ramachandran Graph traversal is not working if field has only docValues since the construction of leaf or parent node queries uses only TermQuery. \\ \\ {code:xml|title=managed-schema|borderStyle=solid} id {code} {code} curl -XPOST -H 'Content-Type: application/json' 'http://localhost:8983/solr/graph/update' --data-binary ' { "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } }, "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } }, "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } }, "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } }, "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } }, "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 Child1" } }, "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 Child2" } }, "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 Child1" } }, "commit" : {} }' {code} {code} http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid to=id}id:1 or http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id to=parentid}id:122 {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Assigned] (SOLR-11190) GraphQuery not working if field has only docValues
[ https://issues.apache.org/jira/browse/SOLR-11190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran reassigned SOLR-11190: --- Assignee: Karthik Ramachandran > GraphQuery not working if field has only docValues > -- > > Key: SOLR-11190 > URL: https://issues.apache.org/jira/browse/SOLR-11190 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: query parsers >Affects Versions: 6.6 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > > Graph traversal is not working if field has only docValues since the > construction of leaf or parent node queries uses only TermQuery. > \\ \\ > {code:xml|title=managed-schema|borderStyle=solid} > > docValues="true" /> > docValues="true" /> > docValues="true" /> > docValues="true" /> > id > > precisionStep="0" positionIncrementGap="0"/> > > {code} > {code} > curl -XPOST -H 'Content-Type: application/json' > 'http://localhost:8983/solr/graph/update' --data-binary ' { > "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, > "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, > "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, > "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } > }, > "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } > }, > "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } > }, > "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } > }, > "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } > }, > "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 > Child1" } }, > "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 > Child2" } }, > "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 > Child1" } }, > "commit" : {} > }' > {code} > {code} > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid > to=id}id:1 > or > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id > to=parentid}id:122 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-11190) GraphQuery not working if field has only docValues
[ https://issues.apache.org/jira/browse/SOLR-11190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11190: Attachment: SOLR-11190.patch > GraphQuery not working if field has only docValues > -- > > Key: SOLR-11190 > URL: https://issues.apache.org/jira/browse/SOLR-11190 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: query parsers >Affects Versions: 6.6 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Attachments: SOLR-11190.patch > > > Graph traversal is not working if field has only docValues since the > construction of leaf or parent node queries uses only TermQuery. > \\ \\ > {code:xml|title=managed-schema|borderStyle=solid} > > docValues="true" /> > docValues="true" /> > docValues="true" /> > docValues="true" /> > id > > precisionStep="0" positionIncrementGap="0"/> > > {code} > {code} > curl -XPOST -H 'Content-Type: application/json' > 'http://localhost:8983/solr/graph/update' --data-binary ' { > "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, > "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, > "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, > "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } > }, > "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } > }, > "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } > }, > "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } > }, > "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } > }, > "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 > Child1" } }, > "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 > Child2" } }, > "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 > Child1" } }, > "commit" : {} > }' > {code} > {code} > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid > to=id}id:1 > or > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id > to=parentid}id:122 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11190) GraphQuery not working if field has only docValues
[ https://issues.apache.org/jira/browse/SOLR-11190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115444#comment-16115444 ] Karthik Ramachandran commented on SOLR-11190: - Agreed, If the field is indexed we should use TermInSetQuery. I have fixed it, you can check it in pull request. I will update the patch soon. > GraphQuery not working if field has only docValues > -- > > Key: SOLR-11190 > URL: https://issues.apache.org/jira/browse/SOLR-11190 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: query parsers >Affects Versions: 6.6 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Attachments: SOLR-11190.patch > > > Graph traversal is not working if field has only docValues since the > construction of leaf or parent node queries uses only TermQuery. > \\ \\ > {code:xml|title=managed-schema|borderStyle=solid} > > docValues="true" /> > docValues="true" /> > docValues="true" /> > docValues="true" /> > id > > precisionStep="0" positionIncrementGap="0"/> > > {code} > {code} > curl -XPOST -H 'Content-Type: application/json' > 'http://localhost:8983/solr/graph/update' --data-binary ' { > "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, > "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, > "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, > "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } > }, > "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } > }, > "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } > }, > "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } > }, > "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } > }, > "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 > Child1" } }, > "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 > Child2" } }, > "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 > Child1" } }, > "commit" : {} > }' > {code} > {code} > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid > to=id}id:1 > or > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id > to=parentid}id:122 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-11190) GraphQuery not working if field has only docValues
[ https://issues.apache.org/jira/browse/SOLR-11190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11190: Attachment: SOLR-11190.patch > GraphQuery not working if field has only docValues > -- > > Key: SOLR-11190 > URL: https://issues.apache.org/jira/browse/SOLR-11190 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: query parsers >Affects Versions: 6.6 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Attachments: SOLR-11190.patch, SOLR-11190.patch > > > Graph traversal is not working if field has only docValues since the > construction of leaf or parent node queries uses only TermQuery. > \\ \\ > {code:xml|title=managed-schema|borderStyle=solid} > > docValues="true" /> > docValues="true" /> > docValues="true" /> > docValues="true" /> > id > > precisionStep="0" positionIncrementGap="0"/> > > {code} > {code} > curl -XPOST -H 'Content-Type: application/json' > 'http://localhost:8983/solr/graph/update' --data-binary ' { > "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, > "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, > "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, > "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } > }, > "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } > }, > "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } > }, > "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } > }, > "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } > }, > "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 > Child1" } }, > "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 > Child2" } }, > "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 > Child1" } }, > "commit" : {} > }' > {code} > {code} > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid > to=id}id:1 > or > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id > to=parentid}id:122 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-11190) GraphQuery not working if field has only docValues
[ https://issues.apache.org/jira/browse/SOLR-11190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11190: Attachment: SOLR-11190.patch > GraphQuery not working if field has only docValues > -- > > Key: SOLR-11190 > URL: https://issues.apache.org/jira/browse/SOLR-11190 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: query parsers >Affects Versions: 6.6 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Attachments: SOLR-11190.patch, SOLR-11190.patch, SOLR-11190.patch, > SOLR-11190.patch > > > Graph traversal is not working if field has only docValues since the > construction of leaf or parent node queries uses only TermQuery. > \\ \\ > {code:xml|title=managed-schema|borderStyle=solid} > > docValues="true" /> > docValues="true" /> > docValues="true" /> > docValues="true" /> > id > > precisionStep="0" positionIncrementGap="0"/> > > {code} > {code} > curl -XPOST -H 'Content-Type: application/json' > 'http://localhost:8983/solr/graph/update' --data-binary ' { > "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, > "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, > "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, > "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } > }, > "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } > }, > "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } > }, > "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } > }, > "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } > }, > "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 > Child1" } }, > "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 > Child2" } }, > "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 > Child1" } }, > "commit" : {} > }' > {code} > {code} > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid > to=id}id:1 > or > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id > to=parentid}id:122 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11190) GraphQuery not working if field has only docValues
[ https://issues.apache.org/jira/browse/SOLR-11190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16119131#comment-16119131 ] Karthik Ramachandran commented on SOLR-11190: - I have updated the patch with the check. > GraphQuery not working if field has only docValues > -- > > Key: SOLR-11190 > URL: https://issues.apache.org/jira/browse/SOLR-11190 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: query parsers >Affects Versions: 6.6 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Attachments: SOLR-11190.patch, SOLR-11190.patch, SOLR-11190.patch, > SOLR-11190.patch > > > Graph traversal is not working if field has only docValues since the > construction of leaf or parent node queries uses only TermQuery. > \\ \\ > {code:xml|title=managed-schema|borderStyle=solid} > > docValues="true" /> > docValues="true" /> > docValues="true" /> > docValues="true" /> > id > > precisionStep="0" positionIncrementGap="0"/> > > {code} > {code} > curl -XPOST -H 'Content-Type: application/json' > 'http://localhost:8983/solr/graph/update' --data-binary ' { > "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, > "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, > "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, > "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } > }, > "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } > }, > "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } > }, > "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } > }, > "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } > }, > "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 > Child1" } }, > "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 > Child2" } }, > "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 > Child1" } }, > "commit" : {} > }' > {code} > {code} > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid > to=id}id:1 > or > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id > to=parentid}id:122 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-11190) GraphQuery not working string fields that has only docValues
[ https://issues.apache.org/jira/browse/SOLR-11190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11190: Summary: GraphQuery not working string fields that has only docValues (was: GraphQuery not working if field has only docValues) > GraphQuery not working string fields that has only docValues > > > Key: SOLR-11190 > URL: https://issues.apache.org/jira/browse/SOLR-11190 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: query parsers >Affects Versions: 6.6 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Attachments: SOLR-11190.patch, SOLR-11190.patch, SOLR-11190.patch, > SOLR-11190.patch > > > Graph traversal is not working if field has only docValues since the > construction of leaf or parent node queries uses only TermQuery. > \\ \\ > {code:xml|title=managed-schema|borderStyle=solid} > > docValues="true" /> > docValues="true" /> > docValues="true" /> > docValues="true" /> > id > > precisionStep="0" positionIncrementGap="0"/> > > {code} > {code} > curl -XPOST -H 'Content-Type: application/json' > 'http://localhost:8983/solr/graph/update' --data-binary ' { > "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, > "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, > "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, > "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } > }, > "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } > }, > "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } > }, > "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } > }, > "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } > }, > "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 > Child1" } }, > "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 > Child2" } }, > "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 > Child1" } }, > "commit" : {} > }' > {code} > {code} > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid > to=id}id:1 > or > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id > to=parentid}id:122 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-11190) GraphQuery not working string fields that has only docValues
[ https://issues.apache.org/jira/browse/SOLR-11190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11190: Description: Graph traversal is not working if string field has only docValues since the construction of leaf or parent node queries uses only TermQuery. \\ \\ {code:xml|title=managed-schema|borderStyle=solid} id {code} {code} curl -XPOST -H 'Content-Type: application/json' 'http://localhost:8983/solr/graph/update' --data-binary ' { "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } }, "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } }, "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } }, "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } }, "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } }, "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 Child1" } }, "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 Child2" } }, "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 Child1" } }, "commit" : {} }' {code} {code} http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid to=id}id:1 or http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id to=parentid}id:122 {code} was: Graph traversal is not working if field has only docValues since the construction of leaf or parent node queries uses only TermQuery. \\ \\ {code:xml|title=managed-schema|borderStyle=solid} id {code} {code} curl -XPOST -H 'Content-Type: application/json' 'http://localhost:8983/solr/graph/update' --data-binary ' { "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } }, "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } }, "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } }, "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } }, "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } }, "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 Child1" } }, "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 Child2" } }, "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 Child1" } }, "commit" : {} }' {code} {code} http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid to=id}id:1 or http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id to=parentid}id:122 {code} > GraphQuery not working string fields that has only docValues > > > Key: SOLR-11190 > URL: https://issues.apache.org/jira/browse/SOLR-11190 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: query parsers >Affects Versions: 6.6 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Attachments: SOLR-11190.patch, SOLR-11190.patch, SOLR-11190.patch, > SOLR-11190.patch > > > Graph traversal is not working if string field has only docValues since the > construction of leaf or parent node queries uses only TermQuery. > \\ \\ > {code:xml|title=managed-schema|borderStyle=solid} > > docValues="true" /> > docValues="true" /> > docValues="true" /> > docValues="true" /> > id > > precisionStep="0" positionIncrementGap="0"/> > > {code} > {code} > curl -XPOST -H 'Content-Type: application/json' > 'http://localhost:8983/solr/graph/update' --data-binary ' { > "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, > "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, > "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, > "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } > }, > "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } > }, > "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } > }, > "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } > }, > "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } > }, > "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 > Child1" } }, > "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 > Child2" } }, > "add" : { "doc" : { "id" : "131", "parentid" : "1
[jira] [Updated] (SOLR-11190) GraphQuery not working for string fields that has only docValues
[ https://issues.apache.org/jira/browse/SOLR-11190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11190: Summary: GraphQuery not working for string fields that has only docValues (was: GraphQuery not working string fields that has only docValues) > GraphQuery not working for string fields that has only docValues > > > Key: SOLR-11190 > URL: https://issues.apache.org/jira/browse/SOLR-11190 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: query parsers >Affects Versions: 6.6 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Attachments: SOLR-11190.patch, SOLR-11190.patch, SOLR-11190.patch, > SOLR-11190.patch > > > Graph traversal is not working if string field has only docValues since the > construction of leaf or parent node queries uses only TermQuery. > \\ \\ > {code:xml|title=managed-schema|borderStyle=solid} > > docValues="true" /> > docValues="true" /> > docValues="true" /> > docValues="true" /> > id > > precisionStep="0" positionIncrementGap="0"/> > > {code} > {code} > curl -XPOST -H 'Content-Type: application/json' > 'http://localhost:8983/solr/graph/update' --data-binary ' { > "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, > "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, > "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, > "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } > }, > "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } > }, > "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } > }, > "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } > }, > "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } > }, > "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 > Child1" } }, > "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 > Child2" } }, > "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 > Child1" } }, > "commit" : {} > }' > {code} > {code} > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid > to=id}id:1 > or > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id > to=parentid}id:122 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-11214) GraphQuery not working for TrieField's that has only docValues
Karthik Ramachandran created SOLR-11214: --- Summary: GraphQuery not working for TrieField's that has only docValues Key: SOLR-11214 URL: https://issues.apache.org/jira/browse/SOLR-11214 Project: Solr Issue Type: Bug Security Level: Public (Default Security Level. Issues are Public) Components: query parsers Affects Versions: 6.6 Reporter: Karthik Ramachandran Assignee: Karthik Ramachandran Graph traversal is not working for TrieField's with only docValues since the construction of leaf or parent node queries uses only TermQuery. \\ \\ {code:xml|title=managed-schema|borderStyle=solid} id {code} {code} curl -XPOST -H 'Content-Type: application/json' 'http://localhost:8983/solr/graph/update' --data-binary ' { "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } }, "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } }, "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } }, "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } }, "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } }, "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 Child1" } }, "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 Child2" } }, "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 Child1" } }, "commit" : {} }' {code} {code} http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid to=id}id:1 or http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id to=parentid}id:122 {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11190) GraphQuery not working for string fields that has only docValues
[ https://issues.apache.org/jira/browse/SOLR-11190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16121614#comment-16121614 ] Karthik Ramachandran commented on SOLR-11190: - Thanks Varun! Can this be pulled in for 7.0 release? > GraphQuery not working for string fields that has only docValues > > > Key: SOLR-11190 > URL: https://issues.apache.org/jira/browse/SOLR-11190 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: query parsers >Affects Versions: 6.6 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Fix For: master (8.0), 7.1 > > Attachments: SOLR-11190.patch, SOLR-11190.patch, SOLR-11190.patch, > SOLR-11190.patch, SOLR-11190.patch, SOLR-11190.patch > > > Graph traversal is not working if string field has only docValues since the > construction of leaf or parent node queries uses only TermQuery. > \\ \\ > {code:xml|title=managed-schema|borderStyle=solid} > > docValues="true" /> > docValues="true" /> > docValues="true" /> > docValues="true" /> > id > > precisionStep="0" positionIncrementGap="0"/> > > {code} > {code} > curl -XPOST -H 'Content-Type: application/json' > 'http://localhost:8983/solr/graph/update' --data-binary ' { > "add" : { "doc" : { "id" : "1", "name" : "Root1" } }, > "add" : { "doc" : { "id" : "2", "name" : "Root2" } }, > "add" : { "doc" : { "id" : "3", "name" : "Root3" } }, > "add" : { "doc" : { "id" : "11", "parentid" : "1", "name" : "Root1 Child1" } > }, > "add" : { "doc" : { "id" : "12", "parentid" : "1", "name" : "Root1 Child2" } > }, > "add" : { "doc" : { "id" : "13", "parentid" : "1", "name" : "Root1 Child3" } > }, > "add" : { "doc" : { "id" : "21", "parentid" : "2", "name" : "Root2 Child1" } > }, > "add" : { "doc" : { "id" : "22", "parentid" : "2", "name" : "Root2 Child2" } > }, > "add" : { "doc" : { "id" : "121", "parentid" : "12", "name" : "Root12 > Child1" } }, > "add" : { "doc" : { "id" : "122", "parentid" : "12", "name" : "Root12 > Child2" } }, > "add" : { "doc" : { "id" : "131", "parentid" : "13", "name" : "Root13 > Child1" } }, > "commit" : {} > }' > {code} > {code} > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=parentid > to=id}id:1 > or > http://localhost:8983/solr/graph/select?q=*:*&fq={!graph from=id > to=parentid}id:122 > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10480) Offset does not allow for full pagination in JSON Facet API
[ https://issues.apache.org/jira/browse/SOLR-10480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981352#comment-15981352 ] Karthik Ramachandran commented on SOLR-10480: - I agree with [~The_matrixme], in my case with shard query facet query does not return result with pagination. I have sample code to demo the issue. https://gist.github.com/mrkarthik/8848dfb54536df4a24103d6939b54f61 > Offset does not allow for full pagination in JSON Facet API > --- > > Key: SOLR-10480 > URL: https://issues.apache.org/jira/browse/SOLR-10480 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Facet Module, SolrCloud >Affects Versions: 6.4.1 >Reporter: Maxime Darçot > > I have a SolrCloud cluster and when I use the JSON facet API to do term > faceting like this: > bq. json.facet={"results":{"type": "terms", "field": "my_field", "limit": > 100, "offset": 100, "numBuckets": true}} > it does work correctly. > However the _numBuckets_ tells me in return that I have more than 6 millions > buckets but as soon as I start to grow the _offset_ value to browse these > buckets, it doesn't return anything anymore (when I reach an offset of around > 300). > What is even weirder is that if I put a bigger _limit_, like 10'000, I can > increase the _offset_ until around 29'000 before it doesn't return anything. > And the returned _numBuckets_ doesn't change all the while. > It is a big problem because we can't paginate till the end of the buckets. > Might be related to SOLR-7452, I don't know... -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-11622) Bundled mime4j library not sufficient for Tika requirement
[ https://issues.apache.org/jira/browse/SOLR-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11622: Attachment: SOLR-11622.patch > Bundled mime4j library not sufficient for Tika requirement > -- > > Key: SOLR-11622 > URL: https://issues.apache.org/jira/browse/SOLR-11622 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Build >Affects Versions: 7.1, 6.6.2 >Reporter: Karim Malhas >Priority: Minor > Labels: build > Attachments: SOLR-11622.patch > > > The version 7.2 of Apache James Mime4j bundled with the Solr binary releases > does not match what is required by Apache Tika for parsing rfc2822 messages. > The master branch for james-mime4j seems to contain the missing Builder class > [https://github.com/apache/james-mime4j/blob/master/core/src/main/java/org/apache/james/mime4j/stream/MimeConfig.java > ] > This prevents import of rfc2822 formatted messages. For example like so: > {{./bin/post -c dovecot -type 'message/rfc822' 'testdata/email_01.txt' > }} > And results in the following stacktrace: > java.lang.NoClassDefFoundError: > org/apache/james/mime4j/stream/MimeConfig$Builder > at > org.apache.tika.parser.mail.RFC822Parser.parse(RFC822Parser.java:63) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:135) > at > org.apache.solr.handler.extraction.ExtractingDocumentLoader.load(ExtractingDocumentLoader.java:228) > at > org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:68) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.
[jira] [Assigned] (SOLR-11622) Bundled mime4j library not sufficient for Tika requirement
[ https://issues.apache.org/jira/browse/SOLR-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran reassigned SOLR-11622: --- Assignee: Karthik Ramachandran > Bundled mime4j library not sufficient for Tika requirement > -- > > Key: SOLR-11622 > URL: https://issues.apache.org/jira/browse/SOLR-11622 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Build >Affects Versions: 7.1, 6.6.2 >Reporter: Karim Malhas >Assignee: Karthik Ramachandran >Priority: Minor > Labels: build > Attachments: SOLR-11622.patch > > > The version 7.2 of Apache James Mime4j bundled with the Solr binary releases > does not match what is required by Apache Tika for parsing rfc2822 messages. > The master branch for james-mime4j seems to contain the missing Builder class > [https://github.com/apache/james-mime4j/blob/master/core/src/main/java/org/apache/james/mime4j/stream/MimeConfig.java > ] > This prevents import of rfc2822 formatted messages. For example like so: > {{./bin/post -c dovecot -type 'message/rfc822' 'testdata/email_01.txt' > }} > And results in the following stacktrace: > java.lang.NoClassDefFoundError: > org/apache/james/mime4j/stream/MimeConfig$Builder > at > org.apache.tika.parser.mail.RFC822Parser.parse(RFC822Parser.java:63) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:135) > at > org.apache.solr.handler.extraction.ExtractingDocumentLoader.load(ExtractingDocumentLoader.java:228) > at > org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:68) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) > at > org.eclipse.jetty.
[jira] [Commented] (SOLR-11622) Bundled mime4j library not sufficient for Tika requirement
[ https://issues.apache.org/jira/browse/SOLR-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272790#comment-16272790 ] Karthik Ramachandran commented on SOLR-11622: - [~talli...@mitre.org] with this patch we were able to process EML files, can you review the changes? > Bundled mime4j library not sufficient for Tika requirement > -- > > Key: SOLR-11622 > URL: https://issues.apache.org/jira/browse/SOLR-11622 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Build >Affects Versions: 7.1, 6.6.2 >Reporter: Karim Malhas >Assignee: Karthik Ramachandran >Priority: Minor > Labels: build > Attachments: SOLR-11622.patch > > > The version 7.2 of Apache James Mime4j bundled with the Solr binary releases > does not match what is required by Apache Tika for parsing rfc2822 messages. > The master branch for james-mime4j seems to contain the missing Builder class > [https://github.com/apache/james-mime4j/blob/master/core/src/main/java/org/apache/james/mime4j/stream/MimeConfig.java > ] > This prevents import of rfc2822 formatted messages. For example like so: > {{./bin/post -c dovecot -type 'message/rfc822' 'testdata/email_01.txt' > }} > And results in the following stacktrace: > java.lang.NoClassDefFoundError: > org/apache/james/mime4j/stream/MimeConfig$Builder > at > org.apache.tika.parser.mail.RFC822Parser.parse(RFC822Parser.java:63) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:135) > at > org.apache.solr.handler.extraction.ExtractingDocumentLoader.load(ExtractingDocumentLoader.java:228) > at > org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:68) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.j
[jira] [Commented] (SOLR-11622) Bundled mime4j library not sufficient for Tika requirement
[ https://issues.apache.org/jira/browse/SOLR-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274648#comment-16274648 ] Karthik Ramachandran commented on SOLR-11622: - I just now read the bug report, we are currently using 6.6.2 and we d'not see any issue with ppt extraction. > Bundled mime4j library not sufficient for Tika requirement > -- > > Key: SOLR-11622 > URL: https://issues.apache.org/jira/browse/SOLR-11622 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Build >Affects Versions: 7.1, 6.6.2 >Reporter: Karim Malhas >Assignee: Karthik Ramachandran >Priority: Minor > Labels: build > Attachments: SOLR-11622.patch > > > The version 7.2 of Apache James Mime4j bundled with the Solr binary releases > does not match what is required by Apache Tika for parsing rfc2822 messages. > The master branch for james-mime4j seems to contain the missing Builder class > [https://github.com/apache/james-mime4j/blob/master/core/src/main/java/org/apache/james/mime4j/stream/MimeConfig.java > ] > This prevents import of rfc2822 formatted messages. For example like so: > {{./bin/post -c dovecot -type 'message/rfc822' 'testdata/email_01.txt' > }} > And results in the following stacktrace: > java.lang.NoClassDefFoundError: > org/apache/james/mime4j/stream/MimeConfig$Builder > at > org.apache.tika.parser.mail.RFC822Parser.parse(RFC822Parser.java:63) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:135) > at > org.apache.solr.handler.extraction.ExtractingDocumentLoader.load(ExtractingDocumentLoader.java:228) > at > org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:68) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.e
[jira] [Commented] (SOLR-11622) Bundled mime4j library not sufficient for Tika requirement
[ https://issues.apache.org/jira/browse/SOLR-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275814#comment-16275814 ] Karthik Ramachandran commented on SOLR-11622: - Updated the patch. https://github.com/apache/lucene-solr/pull/282 > Bundled mime4j library not sufficient for Tika requirement > -- > > Key: SOLR-11622 > URL: https://issues.apache.org/jira/browse/SOLR-11622 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Build >Affects Versions: 7.1, 6.6.2 >Reporter: Karim Malhas >Assignee: Karthik Ramachandran >Priority: Minor > Labels: build > Attachments: SOLR-11622.patch, SOLR-11622.patch > > > The version 7.2 of Apache James Mime4j bundled with the Solr binary releases > does not match what is required by Apache Tika for parsing rfc2822 messages. > The master branch for james-mime4j seems to contain the missing Builder class > [https://github.com/apache/james-mime4j/blob/master/core/src/main/java/org/apache/james/mime4j/stream/MimeConfig.java > ] > This prevents import of rfc2822 formatted messages. For example like so: > {{./bin/post -c dovecot -type 'message/rfc822' 'testdata/email_01.txt' > }} > And results in the following stacktrace: > java.lang.NoClassDefFoundError: > org/apache/james/mime4j/stream/MimeConfig$Builder > at > org.apache.tika.parser.mail.RFC822Parser.parse(RFC822Parser.java:63) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:135) > at > org.apache.solr.handler.extraction.ExtractingDocumentLoader.load(ExtractingDocumentLoader.java:228) > at > org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:68) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.
[jira] [Updated] (SOLR-11622) Bundled mime4j library not sufficient for Tika requirement
[ https://issues.apache.org/jira/browse/SOLR-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11622: Attachment: SOLR-11622.patch > Bundled mime4j library not sufficient for Tika requirement > -- > > Key: SOLR-11622 > URL: https://issues.apache.org/jira/browse/SOLR-11622 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Build >Affects Versions: 7.1, 6.6.2 >Reporter: Karim Malhas >Assignee: Karthik Ramachandran >Priority: Minor > Labels: build > Attachments: SOLR-11622.patch, SOLR-11622.patch > > > The version 7.2 of Apache James Mime4j bundled with the Solr binary releases > does not match what is required by Apache Tika for parsing rfc2822 messages. > The master branch for james-mime4j seems to contain the missing Builder class > [https://github.com/apache/james-mime4j/blob/master/core/src/main/java/org/apache/james/mime4j/stream/MimeConfig.java > ] > This prevents import of rfc2822 formatted messages. For example like so: > {{./bin/post -c dovecot -type 'message/rfc822' 'testdata/email_01.txt' > }} > And results in the following stacktrace: > java.lang.NoClassDefFoundError: > org/apache/james/mime4j/stream/MimeConfig$Builder > at > org.apache.tika.parser.mail.RFC822Parser.parse(RFC822Parser.java:63) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:135) > at > org.apache.solr.handler.extraction.ExtractingDocumentLoader.load(ExtractingDocumentLoader.java:228) > at > org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:68) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) > at > org.eclip
[jira] [Comment Edited] (SOLR-11622) Bundled mime4j library not sufficient for Tika requirement
[ https://issues.apache.org/jira/browse/SOLR-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275814#comment-16275814 ] Karthik Ramachandran edited comment on SOLR-11622 at 12/4/17 3:49 PM: -- Updated the patch. [~talli...@mitre.org] Can you run the test cases now and check if this patch is good? https://github.com/apache/lucene-solr/pull/282 was (Author: kramachand...@commvault.com): Updated the patch. https://github.com/apache/lucene-solr/pull/282 > Bundled mime4j library not sufficient for Tika requirement > -- > > Key: SOLR-11622 > URL: https://issues.apache.org/jira/browse/SOLR-11622 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Build >Affects Versions: 7.1, 6.6.2 >Reporter: Karim Malhas >Assignee: Karthik Ramachandran >Priority: Minor > Labels: build > Attachments: SOLR-11622.patch, SOLR-11622.patch > > > The version 7.2 of Apache James Mime4j bundled with the Solr binary releases > does not match what is required by Apache Tika for parsing rfc2822 messages. > The master branch for james-mime4j seems to contain the missing Builder class > [https://github.com/apache/james-mime4j/blob/master/core/src/main/java/org/apache/james/mime4j/stream/MimeConfig.java > ] > This prevents import of rfc2822 formatted messages. For example like so: > {{./bin/post -c dovecot -type 'message/rfc822' 'testdata/email_01.txt' > }} > And results in the following stacktrace: > java.lang.NoClassDefFoundError: > org/apache/james/mime4j/stream/MimeConfig$Builder > at > org.apache.tika.parser.mail.RFC822Parser.parse(RFC822Parser.java:63) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:135) > at > org.apache.solr.handler.extraction.ExtractingDocumentLoader.load(ExtractingDocumentLoader.java:228) > at > org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:68) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strateg
[jira] [Updated] (SOLR-11304) Exception while returning document if LatLonPointSpatialField field is not stored
[ https://issues.apache.org/jira/browse/SOLR-11304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11304: Attachment: (was: SOLR-11304.patch) > Exception while returning document if LatLonPointSpatialField field is not > stored > - > > Key: SOLR-11304 > URL: https://issues.apache.org/jira/browse/SOLR-11304 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6, 7.0 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Attachments: SOLR-11304.patch > > > NullPointerException while retrieving the document if LatLonPointSpatialField > is not stored > {code:xml} > docValues="true"/> > stored="false"/> > {code} > {code} > 2017-08-31 12:18:23.368 ERROR (qtp1866850137-23) [ x:latlon] > o.a.s.s.HttpSolrCall null:java.lang.NullPointerException > at > org.apache.solr.search.SolrDocumentFetcher.decorateDocValueFields(SolrDocumentFetcher.java:510) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:160) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:1) > at > org.apache.solr.response.TextResponseWriter.writeDocuments(TextResponseWriter.java:275) > at > org.apache.solr.response.TextResponseWriter.writeVal(TextResponseWriter.java:161) > at > org.apache.solr.response.JSONWriter.writeNamedListAsMapWithDups(JSONResponseWriter.java:209) > at > org.apache.solr.response.JSONWriter.writeNamedList(JSONResponseWriter.java:325) > at > org.apache.solr.response.JSONWriter.writeResponse(JSONResponseWriter.java:120) > at > org.apache.solr.response.JSONResponseWriter.write(JSONResponseWriter.java:71) > at > org.apache.solr.response.QueryResponseWriterUtil.writeQueryResponse(QueryResponseWriterUtil.java:65) > at > org.apache.solr.servlet.HttpSolrCall.writeResponse(HttpSolrCall.java:806) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:535) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) > at > org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) > at java.lang.Thread.run(Unknown Source) > {code}
[jira] [Updated] (SOLR-11304) Exception while returning document if LatLonPointSpatialField field is not stored
[ https://issues.apache.org/jira/browse/SOLR-11304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11304: Attachment: SOLR-11304.patch > Exception while returning document if LatLonPointSpatialField field is not > stored > - > > Key: SOLR-11304 > URL: https://issues.apache.org/jira/browse/SOLR-11304 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6, 7.0 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Attachments: SOLR-11304.patch > > > NullPointerException while retrieving the document if LatLonPointSpatialField > is not stored > {code:xml} > docValues="true"/> > stored="false"/> > {code} > {code} > 2017-08-31 12:18:23.368 ERROR (qtp1866850137-23) [ x:latlon] > o.a.s.s.HttpSolrCall null:java.lang.NullPointerException > at > org.apache.solr.search.SolrDocumentFetcher.decorateDocValueFields(SolrDocumentFetcher.java:510) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:160) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:1) > at > org.apache.solr.response.TextResponseWriter.writeDocuments(TextResponseWriter.java:275) > at > org.apache.solr.response.TextResponseWriter.writeVal(TextResponseWriter.java:161) > at > org.apache.solr.response.JSONWriter.writeNamedListAsMapWithDups(JSONResponseWriter.java:209) > at > org.apache.solr.response.JSONWriter.writeNamedList(JSONResponseWriter.java:325) > at > org.apache.solr.response.JSONWriter.writeResponse(JSONResponseWriter.java:120) > at > org.apache.solr.response.JSONResponseWriter.write(JSONResponseWriter.java:71) > at > org.apache.solr.response.QueryResponseWriterUtil.writeQueryResponse(QueryResponseWriterUtil.java:65) > at > org.apache.solr.servlet.HttpSolrCall.writeResponse(HttpSolrCall.java:806) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:535) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) > at > org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) > at java.lang.Thread.run(Unknown Source) > {code} -- This m
[jira] [Commented] (SOLR-11304) Exception while returning document if LatLonPointSpatialField field is not stored
[ https://issues.apache.org/jira/browse/SOLR-11304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279629#comment-16279629 ] Karthik Ramachandran commented on SOLR-11304: - [~dsmiley] I checked SOLR-11532, seems like fix is there to avoid NPE and not to return the values in the response. Do we still have to use {{stored=true}} if we have to retrieve the lat lon values? > Exception while returning document if LatLonPointSpatialField field is not > stored > - > > Key: SOLR-11304 > URL: https://issues.apache.org/jira/browse/SOLR-11304 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6, 7.0 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Fix For: 7.2 > > Attachments: SOLR-11304.patch > > > NullPointerException while retrieving the document if LatLonPointSpatialField > is not stored > {code:xml} > docValues="true"/> > stored="false"/> > {code} > {code} > 2017-08-31 12:18:23.368 ERROR (qtp1866850137-23) [ x:latlon] > o.a.s.s.HttpSolrCall null:java.lang.NullPointerException > at > org.apache.solr.search.SolrDocumentFetcher.decorateDocValueFields(SolrDocumentFetcher.java:510) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:160) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:1) > at > org.apache.solr.response.TextResponseWriter.writeDocuments(TextResponseWriter.java:275) > at > org.apache.solr.response.TextResponseWriter.writeVal(TextResponseWriter.java:161) > at > org.apache.solr.response.JSONWriter.writeNamedListAsMapWithDups(JSONResponseWriter.java:209) > at > org.apache.solr.response.JSONWriter.writeNamedList(JSONResponseWriter.java:325) > at > org.apache.solr.response.JSONWriter.writeResponse(JSONResponseWriter.java:120) > at > org.apache.solr.response.JSONResponseWriter.write(JSONResponseWriter.java:71) > at > org.apache.solr.response.QueryResponseWriterUtil.writeQueryResponse(QueryResponseWriterUtil.java:65) > at > org.apache.solr.servlet.HttpSolrCall.writeResponse(HttpSolrCall.java:806) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:535) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) >
[jira] [Commented] (SOLR-11304) Exception while returning document if LatLonPointSpatialField field is not stored
[ https://issues.apache.org/jira/browse/SOLR-11304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280228#comment-16280228 ] Karthik Ramachandran commented on SOLR-11304: - [~dsmiley] Is there any reason that we don't decode from docValues? In my patch I have decoded lat-lon from docValues, can you check the patch? > Exception while returning document if LatLonPointSpatialField field is not > stored > - > > Key: SOLR-11304 > URL: https://issues.apache.org/jira/browse/SOLR-11304 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6, 7.0 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Fix For: 7.2 > > Attachments: SOLR-11304.patch > > > NullPointerException while retrieving the document if LatLonPointSpatialField > is not stored > {code:xml} > docValues="true"/> > stored="false"/> > {code} > {code} > 2017-08-31 12:18:23.368 ERROR (qtp1866850137-23) [ x:latlon] > o.a.s.s.HttpSolrCall null:java.lang.NullPointerException > at > org.apache.solr.search.SolrDocumentFetcher.decorateDocValueFields(SolrDocumentFetcher.java:510) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:160) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:1) > at > org.apache.solr.response.TextResponseWriter.writeDocuments(TextResponseWriter.java:275) > at > org.apache.solr.response.TextResponseWriter.writeVal(TextResponseWriter.java:161) > at > org.apache.solr.response.JSONWriter.writeNamedListAsMapWithDups(JSONResponseWriter.java:209) > at > org.apache.solr.response.JSONWriter.writeNamedList(JSONResponseWriter.java:325) > at > org.apache.solr.response.JSONWriter.writeResponse(JSONResponseWriter.java:120) > at > org.apache.solr.response.JSONResponseWriter.write(JSONResponseWriter.java:71) > at > org.apache.solr.response.QueryResponseWriterUtil.writeQueryResponse(QueryResponseWriterUtil.java:65) > at > org.apache.solr.servlet.HttpSolrCall.writeResponse(HttpSolrCall.java:806) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:535) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) > at > org.eclipse.jetty.util.thread.QueuedThreadPoo
[jira] [Commented] (SOLR-11304) Exception while returning document if LatLonPointSpatialField field is not stored
[ https://issues.apache.org/jira/browse/SOLR-11304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280898#comment-16280898 ] Karthik Ramachandran commented on SOLR-11304: - Sure, will submit it sometime this week > Exception while returning document if LatLonPointSpatialField field is not > stored > - > > Key: SOLR-11304 > URL: https://issues.apache.org/jira/browse/SOLR-11304 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6, 7.0 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Fix For: 7.2 > > Attachments: SOLR-11304.patch > > > NullPointerException while retrieving the document if LatLonPointSpatialField > is not stored > {code:xml} > docValues="true"/> > stored="false"/> > {code} > {code} > 2017-08-31 12:18:23.368 ERROR (qtp1866850137-23) [ x:latlon] > o.a.s.s.HttpSolrCall null:java.lang.NullPointerException > at > org.apache.solr.search.SolrDocumentFetcher.decorateDocValueFields(SolrDocumentFetcher.java:510) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:160) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:1) > at > org.apache.solr.response.TextResponseWriter.writeDocuments(TextResponseWriter.java:275) > at > org.apache.solr.response.TextResponseWriter.writeVal(TextResponseWriter.java:161) > at > org.apache.solr.response.JSONWriter.writeNamedListAsMapWithDups(JSONResponseWriter.java:209) > at > org.apache.solr.response.JSONWriter.writeNamedList(JSONResponseWriter.java:325) > at > org.apache.solr.response.JSONWriter.writeResponse(JSONResponseWriter.java:120) > at > org.apache.solr.response.JSONResponseWriter.write(JSONResponseWriter.java:71) > at > org.apache.solr.response.QueryResponseWriterUtil.writeQueryResponse(QueryResponseWriterUtil.java:65) > at > org.apache.solr.servlet.HttpSolrCall.writeResponse(HttpSolrCall.java:806) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:535) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) > at > org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(Qu
[jira] [Updated] (SOLR-11331) Ability to Debug Solr With Eclipse IDE
[ https://issues.apache.org/jira/browse/SOLR-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11331: Attachment: SOLR-11331.patch > Ability to Debug Solr With Eclipse IDE > -- > > Key: SOLR-11331 > URL: https://issues.apache.org/jira/browse/SOLR-11331 > Project: Solr > Issue Type: Improvement >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran >Priority: Minor > Attachments: SOLR-11331.patch > > > Ability to Debug Solr With Eclipse IDE -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11331) Ability to Debug Solr With Eclipse IDE
[ https://issues.apache.org/jira/browse/SOLR-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281908#comment-16281908 ] Karthik Ramachandran commented on SOLR-11331: - I have added ability to start Solr within eclipse and also run JUnit test cases which are useful for debugging. > Ability to Debug Solr With Eclipse IDE > -- > > Key: SOLR-11331 > URL: https://issues.apache.org/jira/browse/SOLR-11331 > Project: Solr > Issue Type: Improvement >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran >Priority: Minor > Attachments: SOLR-11331.patch > > > Ability to Debug Solr With Eclipse IDE -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11331) Ability to Debug Solr With Eclipse IDE
[ https://issues.apache.org/jira/browse/SOLR-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282622#comment-16282622 ] Karthik Ramachandran commented on SOLR-11331: - No, we need to run only "ant eclipse" with this patch. I was able to launch the webapps with this patch. > Ability to Debug Solr With Eclipse IDE > -- > > Key: SOLR-11331 > URL: https://issues.apache.org/jira/browse/SOLR-11331 > Project: Solr > Issue Type: Improvement >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran >Priority: Minor > Attachments: SOLR-11331.patch > > > Ability to Debug Solr With Eclipse IDE -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11331) Ability to Debug Solr With Eclipse IDE
[ https://issues.apache.org/jira/browse/SOLR-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16283005#comment-16283005 ] Karthik Ramachandran commented on SOLR-11331: - Yes, you will see the changes without running any ant tasks. Even while debugging the changes will be hot swapped and can see the change. The only time you need to run "ant eclipse" again is when you change or upgrade dependency version. > Ability to Debug Solr With Eclipse IDE > -- > > Key: SOLR-11331 > URL: https://issues.apache.org/jira/browse/SOLR-11331 > Project: Solr > Issue Type: Improvement >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran >Priority: Minor > Attachments: SOLR-11331.patch > > > Ability to Debug Solr With Eclipse IDE -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11622) Bundled mime4j library not sufficient for Tika requirement
[ https://issues.apache.org/jira/browse/SOLR-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291042#comment-16291042 ] Karthik Ramachandran commented on SOLR-11622: - [~talli...@mitre.org] who can help us review and commit the change? can you? > Bundled mime4j library not sufficient for Tika requirement > -- > > Key: SOLR-11622 > URL: https://issues.apache.org/jira/browse/SOLR-11622 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Build >Affects Versions: 7.1, 6.6.2 >Reporter: Karim Malhas >Assignee: Karthik Ramachandran >Priority: Minor > Labels: build > Attachments: SOLR-11622.patch, SOLR-11622.patch > > > The version 7.2 of Apache James Mime4j bundled with the Solr binary releases > does not match what is required by Apache Tika for parsing rfc2822 messages. > The master branch for james-mime4j seems to contain the missing Builder class > [https://github.com/apache/james-mime4j/blob/master/core/src/main/java/org/apache/james/mime4j/stream/MimeConfig.java > ] > This prevents import of rfc2822 formatted messages. For example like so: > {{./bin/post -c dovecot -type 'message/rfc822' 'testdata/email_01.txt' > }} > And results in the following stacktrace: > java.lang.NoClassDefFoundError: > org/apache/james/mime4j/stream/MimeConfig$Builder > at > org.apache.tika.parser.mail.RFC822Parser.parse(RFC822Parser.java:63) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:135) > at > org.apache.solr.handler.extraction.ExtractingDocumentLoader.load(ExtractingDocumentLoader.java:228) > at > org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:68) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.ut
[jira] [Updated] (SOLR-11331) Ability to Debug Solr With Eclipse IDE
[ https://issues.apache.org/jira/browse/SOLR-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11331: Attachment: SOLR-11331.patch > Ability to Debug Solr With Eclipse IDE > -- > > Key: SOLR-11331 > URL: https://issues.apache.org/jira/browse/SOLR-11331 > Project: Solr > Issue Type: Improvement >Affects Versions: 6.6.2 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran >Priority: Minor > Labels: eclipse > Attachments: SOLR-11331.patch, SOLR-11331.patch > > > Ability to Debug Solr With Eclipse IDE -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11622) Bundled mime4j library not sufficient for Tika requirement
[ https://issues.apache.org/jira/browse/SOLR-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291443#comment-16291443 ] Karthik Ramachandran commented on SOLR-11622: - [~talli...@mitre.org] i am going on vacation, will be back only after Christmas, I can work on it after that. After upgrade, do you have any specific test cases to run? I don't have much test documents or test cases for TIKA. > Bundled mime4j library not sufficient for Tika requirement > -- > > Key: SOLR-11622 > URL: https://issues.apache.org/jira/browse/SOLR-11622 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Build >Affects Versions: 7.1, 6.6.2 >Reporter: Karim Malhas >Assignee: Karthik Ramachandran >Priority: Minor > Labels: build > Attachments: SOLR-11622.patch, SOLR-11622.patch > > > The version 7.2 of Apache James Mime4j bundled with the Solr binary releases > does not match what is required by Apache Tika for parsing rfc2822 messages. > The master branch for james-mime4j seems to contain the missing Builder class > [https://github.com/apache/james-mime4j/blob/master/core/src/main/java/org/apache/james/mime4j/stream/MimeConfig.java > ] > This prevents import of rfc2822 formatted messages. For example like so: > {{./bin/post -c dovecot -type 'message/rfc822' 'testdata/email_01.txt' > }} > And results in the following stacktrace: > java.lang.NoClassDefFoundError: > org/apache/james/mime4j/stream/MimeConfig$Builder > at > org.apache.tika.parser.mail.RFC822Parser.parse(RFC822Parser.java:63) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:135) > at > org.apache.solr.handler.extraction.ExtractingDocumentLoader.load(ExtractingDocumentLoader.java:228) > at > org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:68) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) >
[jira] [Commented] (SOLR-11622) Bundled mime4j library not sufficient for Tika requirement
[ https://issues.apache.org/jira/browse/SOLR-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291516#comment-16291516 ] Karthik Ramachandran commented on SOLR-11622: - I don't mind, if you have time go ahead. > Bundled mime4j library not sufficient for Tika requirement > -- > > Key: SOLR-11622 > URL: https://issues.apache.org/jira/browse/SOLR-11622 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Build >Affects Versions: 7.1, 6.6.2 >Reporter: Karim Malhas >Assignee: Karthik Ramachandran >Priority: Minor > Labels: build > Attachments: SOLR-11622.patch, SOLR-11622.patch > > > The version 7.2 of Apache James Mime4j bundled with the Solr binary releases > does not match what is required by Apache Tika for parsing rfc2822 messages. > The master branch for james-mime4j seems to contain the missing Builder class > [https://github.com/apache/james-mime4j/blob/master/core/src/main/java/org/apache/james/mime4j/stream/MimeConfig.java > ] > This prevents import of rfc2822 formatted messages. For example like so: > {{./bin/post -c dovecot -type 'message/rfc822' 'testdata/email_01.txt' > }} > And results in the following stacktrace: > java.lang.NoClassDefFoundError: > org/apache/james/mime4j/stream/MimeConfig$Builder > at > org.apache.tika.parser.mail.RFC822Parser.parse(RFC822Parser.java:63) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:135) > at > org.apache.solr.handler.extraction.ExtractingDocumentLoader.load(ExtractingDocumentLoader.java:228) > at > org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:68) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceCon
[jira] [Commented] (SOLR-11622) Bundled mime4j library not sufficient for Tika requirement
[ https://issues.apache.org/jira/browse/SOLR-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291959#comment-16291959 ] Karthik Ramachandran commented on SOLR-11622: - Thanks for creating the patch! > Bundled mime4j library not sufficient for Tika requirement > -- > > Key: SOLR-11622 > URL: https://issues.apache.org/jira/browse/SOLR-11622 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: Build >Affects Versions: 7.1, 6.6.2 >Reporter: Karim Malhas >Assignee: Karthik Ramachandran >Priority: Minor > Labels: build > Attachments: SOLR-11622.patch, SOLR-11622.patch > > > The version 7.2 of Apache James Mime4j bundled with the Solr binary releases > does not match what is required by Apache Tika for parsing rfc2822 messages. > The master branch for james-mime4j seems to contain the missing Builder class > [https://github.com/apache/james-mime4j/blob/master/core/src/main/java/org/apache/james/mime4j/stream/MimeConfig.java > ] > This prevents import of rfc2822 formatted messages. For example like so: > {{./bin/post -c dovecot -type 'message/rfc822' 'testdata/email_01.txt' > }} > And results in the following stacktrace: > java.lang.NoClassDefFoundError: > org/apache/james/mime4j/stream/MimeConfig$Builder > at > org.apache.tika.parser.mail.RFC822Parser.parse(RFC822Parser.java:63) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) > at > org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:135) > at > org.apache.solr.handler.extraction.ExtractingDocumentLoader.load(ExtractingDocumentLoader.java:228) > at > org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:68) > at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:173) > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2477) > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:723) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:529) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:361) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:305) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(E
[jira] [Updated] (SOLR-11304) Exception while returning document if LatLonPointSpatialField field is not stored
[ https://issues.apache.org/jira/browse/SOLR-11304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11304: Attachment: SOLR-11304.patch SOLR-11304: Fix Exception while returning document if LatLonPointSpatialField field is not stored > Exception while returning document if LatLonPointSpatialField field is not > stored > - > > Key: SOLR-11304 > URL: https://issues.apache.org/jira/browse/SOLR-11304 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6, 7.0 >Reporter: Karthik Ramachandran > Attachments: SOLR-11304.patch > > > NullPointerException while retrieving the document if LatLonPointSpatialField > is not stored > {code:xml} > docValues="true"/> > stored="false"/> > {code} > {code} > 2017-08-31 12:18:23.368 ERROR (qtp1866850137-23) [ x:latlon] > o.a.s.s.HttpSolrCall null:java.lang.NullPointerException > at > org.apache.solr.search.SolrDocumentFetcher.decorateDocValueFields(SolrDocumentFetcher.java:510) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:160) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:1) > at > org.apache.solr.response.TextResponseWriter.writeDocuments(TextResponseWriter.java:275) > at > org.apache.solr.response.TextResponseWriter.writeVal(TextResponseWriter.java:161) > at > org.apache.solr.response.JSONWriter.writeNamedListAsMapWithDups(JSONResponseWriter.java:209) > at > org.apache.solr.response.JSONWriter.writeNamedList(JSONResponseWriter.java:325) > at > org.apache.solr.response.JSONWriter.writeResponse(JSONResponseWriter.java:120) > at > org.apache.solr.response.JSONResponseWriter.write(JSONResponseWriter.java:71) > at > org.apache.solr.response.QueryResponseWriterUtil.writeQueryResponse(QueryResponseWriterUtil.java:65) > at > org.apache.solr.servlet.HttpSolrCall.writeResponse(HttpSolrCall.java:806) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:535) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) > at > org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) > at ja
[jira] [Created] (SOLR-11331) Ability to Debug Solr With Eclipse IDE
Karthik Ramachandran created SOLR-11331: --- Summary: Ability to Debug Solr With Eclipse IDE Key: SOLR-11331 URL: https://issues.apache.org/jira/browse/SOLR-11331 Project: Solr Issue Type: Improvement Reporter: Karthik Ramachandran Assignee: Karthik Ramachandran Priority: Minor Ability to Debug Solr With Eclipse IDE -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11331) Ability to Debug Solr With Eclipse IDE
[ https://issues.apache.org/jira/browse/SOLR-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155789#comment-16155789 ] Karthik Ramachandran commented on SOLR-11331: - [~erickerickson] This is not a question, I created the JIRA to add eclipse launch files and ant changes to support it. > Ability to Debug Solr With Eclipse IDE > -- > > Key: SOLR-11331 > URL: https://issues.apache.org/jira/browse/SOLR-11331 > Project: Solr > Issue Type: Improvement >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran >Priority: Minor > > Ability to Debug Solr With Eclipse IDE -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Reopened] (SOLR-11331) Ability to Debug Solr With Eclipse IDE
[ https://issues.apache.org/jira/browse/SOLR-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran reopened SOLR-11331: - Re-Opening since its not a question, JIRA is to add eclipse launch files and ant changes to support the ability to debug within IDE. > Ability to Debug Solr With Eclipse IDE > -- > > Key: SOLR-11331 > URL: https://issues.apache.org/jira/browse/SOLR-11331 > Project: Solr > Issue Type: Improvement >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran >Priority: Minor > > Ability to Debug Solr With Eclipse IDE -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Assigned] (SOLR-11304) Exception while returning document if LatLonPointSpatialField field is not stored
[ https://issues.apache.org/jira/browse/SOLR-11304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran reassigned SOLR-11304: --- Assignee: Karthik Ramachandran > Exception while returning document if LatLonPointSpatialField field is not > stored > - > > Key: SOLR-11304 > URL: https://issues.apache.org/jira/browse/SOLR-11304 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6, 7.0 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Attachments: SOLR-11304.patch > > > NullPointerException while retrieving the document if LatLonPointSpatialField > is not stored > {code:xml} > docValues="true"/> > stored="false"/> > {code} > {code} > 2017-08-31 12:18:23.368 ERROR (qtp1866850137-23) [ x:latlon] > o.a.s.s.HttpSolrCall null:java.lang.NullPointerException > at > org.apache.solr.search.SolrDocumentFetcher.decorateDocValueFields(SolrDocumentFetcher.java:510) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:160) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:1) > at > org.apache.solr.response.TextResponseWriter.writeDocuments(TextResponseWriter.java:275) > at > org.apache.solr.response.TextResponseWriter.writeVal(TextResponseWriter.java:161) > at > org.apache.solr.response.JSONWriter.writeNamedListAsMapWithDups(JSONResponseWriter.java:209) > at > org.apache.solr.response.JSONWriter.writeNamedList(JSONResponseWriter.java:325) > at > org.apache.solr.response.JSONWriter.writeResponse(JSONResponseWriter.java:120) > at > org.apache.solr.response.JSONResponseWriter.write(JSONResponseWriter.java:71) > at > org.apache.solr.response.QueryResponseWriterUtil.writeQueryResponse(QueryResponseWriterUtil.java:65) > at > org.apache.solr.servlet.HttpSolrCall.writeResponse(HttpSolrCall.java:806) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:535) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) > at > org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) > at java.lang.Thread.run(Unknown Source) > {code}
[jira] [Commented] (SOLR-11304) Exception while returning document if LatLonPointSpatialField field is not stored
[ https://issues.apache.org/jira/browse/SOLR-11304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184293#comment-16184293 ] Karthik Ramachandran commented on SOLR-11304: - Can someone review the changes? > Exception while returning document if LatLonPointSpatialField field is not > stored > - > > Key: SOLR-11304 > URL: https://issues.apache.org/jira/browse/SOLR-11304 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Affects Versions: 6.6, 7.0 >Reporter: Karthik Ramachandran >Assignee: Karthik Ramachandran > Attachments: SOLR-11304.patch > > > NullPointerException while retrieving the document if LatLonPointSpatialField > is not stored > {code:xml} > docValues="true"/> > stored="false"/> > {code} > {code} > 2017-08-31 12:18:23.368 ERROR (qtp1866850137-23) [ x:latlon] > o.a.s.s.HttpSolrCall null:java.lang.NullPointerException > at > org.apache.solr.search.SolrDocumentFetcher.decorateDocValueFields(SolrDocumentFetcher.java:510) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:160) > at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:1) > at > org.apache.solr.response.TextResponseWriter.writeDocuments(TextResponseWriter.java:275) > at > org.apache.solr.response.TextResponseWriter.writeVal(TextResponseWriter.java:161) > at > org.apache.solr.response.JSONWriter.writeNamedListAsMapWithDups(JSONResponseWriter.java:209) > at > org.apache.solr.response.JSONWriter.writeNamedList(JSONResponseWriter.java:325) > at > org.apache.solr.response.JSONWriter.writeResponse(JSONResponseWriter.java:120) > at > org.apache.solr.response.JSONResponseWriter.write(JSONResponseWriter.java:71) > at > org.apache.solr.response.QueryResponseWriterUtil.writeQueryResponse(QueryResponseWriterUtil.java:65) > at > org.apache.solr.servlet.HttpSolrCall.writeResponse(HttpSolrCall.java:806) > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:535) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:382) > at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:326) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) > at org.eclipse.jetty.server.Server.handle(Server.java:534) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) > at > org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) > at j
[jira] [Assigned] (SOLR-11331) Ability to Debug Solr With Eclipse IDE
[ https://issues.apache.org/jira/browse/SOLR-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran reassigned SOLR-11331: --- Assignee: (was: Karthik Ramachandran) > Ability to Debug Solr With Eclipse IDE > -- > > Key: SOLR-11331 > URL: https://issues.apache.org/jira/browse/SOLR-11331 > Project: Solr > Issue Type: Improvement >Affects Versions: 6.6.2 >Reporter: Karthik Ramachandran >Priority: Minor > Labels: eclipse > Attachments: SOLR-11331.patch, SOLR-11331.patch > > > Ability to Debug Solr With Eclipse IDE -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11331) Ability to Debug Solr With Eclipse IDE
[ https://issues.apache.org/jira/browse/SOLR-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315044#comment-16315044 ] Karthik Ramachandran commented on SOLR-11331: - [~dsmiley], [~ichattopadhyaya] can either of you review the changes and commit them? > Ability to Debug Solr With Eclipse IDE > -- > > Key: SOLR-11331 > URL: https://issues.apache.org/jira/browse/SOLR-11331 > Project: Solr > Issue Type: Improvement >Affects Versions: 6.6.2 >Reporter: Karthik Ramachandran >Priority: Minor > Labels: eclipse > Attachments: SOLR-11331.patch, SOLR-11331.patch > > > Ability to Debug Solr With Eclipse IDE -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-11935) Streaming Expressions shortestPath return stream of tuples
Karthik Ramachandran created SOLR-11935: --- Summary: Streaming Expressions shortestPath return stream of tuples Key: SOLR-11935 URL: https://issues.apache.org/jira/browse/SOLR-11935 Project: Solr Issue Type: Improvement Security Level: Public (Default Security Level. Issues are Public) Components: streaming expressions Affects Versions: 6.6.2, 7.2 Reporter: Karthik Ramachandran Streaming Expressions shortestPath does not return stream of tuples, so it cannot be used other decorators like fetch. [link Mail|http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201801.mbox/%3CCAE4tqLOWYrC18P4HVkUhN2ebrWLqbskg3wQ%3Dw2DLY0M_fbXJaw%40mail.gmail.com%3E] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-11935) Streaming Expressions shortestPath return stream of tuples
[ https://issues.apache.org/jira/browse/SOLR-11935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11935: Description: Streaming Expressions shortestPath does not return stream of tuples, so it cannot be used other decorators like fetch. http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201801.mbox/%3CCAE4tqLOWYrC18P4HVkUhN2ebrWLqbskg3wQ%3Dw2DLY0M_fbXJaw%40mail.gmail.com%3E was: Streaming Expressions shortestPath does not return stream of tuples, so it cannot be used other decorators like fetch. [link Mail|http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201801.mbox/%3CCAE4tqLOWYrC18P4HVkUhN2ebrWLqbskg3wQ%3Dw2DLY0M_fbXJaw%40mail.gmail.com%3E] > Streaming Expressions shortestPath return stream of tuples > -- > > Key: SOLR-11935 > URL: https://issues.apache.org/jira/browse/SOLR-11935 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: streaming expressions >Affects Versions: 7.2, 6.6.2 >Reporter: Karthik Ramachandran >Priority: Major > > Streaming Expressions shortestPath does not return stream of tuples, so it > cannot be used other decorators like fetch. > http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201801.mbox/%3CCAE4tqLOWYrC18P4HVkUhN2ebrWLqbskg3wQ%3Dw2DLY0M_fbXJaw%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-11731) LatLonPointSpatialField could be improved to return the lat/lon from docValues
[ https://issues.apache.org/jira/browse/SOLR-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Ramachandran updated SOLR-11731: Attachment: SOLR-11731.patch > LatLonPointSpatialField could be improved to return the lat/lon from docValues > -- > > Key: SOLR-11731 > URL: https://issues.apache.org/jira/browse/SOLR-11731 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: spatial >Reporter: David Smiley >Priority: Minor > Attachments: SOLR-11731.patch > > > You can only return the lat & lon from a LatLonPointSpatialField if you set > stored=true. But we could allow this (albeit at a small loss in precision) > if stored=false and docValues=true. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-11731) LatLonPointSpatialField could be improved to return the lat/lon from docValues
[ https://issues.apache.org/jira/browse/SOLR-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363101#comment-16363101 ] Karthik Ramachandran commented on SOLR-11731: - Okay, Thanks! > LatLonPointSpatialField could be improved to return the lat/lon from docValues > -- > > Key: SOLR-11731 > URL: https://issues.apache.org/jira/browse/SOLR-11731 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: spatial >Reporter: David Smiley >Priority: Minor > Attachments: SOLR-11731.patch > > Time Spent: 10m > Remaining Estimate: 0h > > You can only return the lat & lon from a LatLonPointSpatialField if you set > stored=true. But we could allow this (albeit at a small loss in precision) > if stored=false and docValues=true. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org