Re: Exception while using {!cardinality=1.0}.
: Can you please explain how having the same field for query and stat can : cause some issue for my better understanding of this feature? I don't know if it can, it probably shouldn't, but in terms of trying ot udnerstand the bug and reproduce it, any pertinant facts may be relivant - particularly the unusual ones. if no one else has ever seen a bug in X, but you were doing something unusual with X, and you get a bug 100% of the time, then that suggests that your unusual usecase would be a very important place to start looking -- so when you posted an example that looks weird nad unusual and unlike any typical usecase of field stats, i wanted ot understand what exactly you were doing and how much of that example was "real" and how much was just you munging your "real" query to hide something yo udidn't wnat to share. -Hoss http://www.lucidworks.com/
Re: Exception while using {!cardinality=1.0}.
- Did you have the exact same data in both fields?
No the data is not same.
- Did your "real" query actually compute stats on the same field you had
: done your main term query on?
The query field is different and I missed to clearly put it. I will
accordingly modify the jira.
So the query can be
q=anyfield:query&stats=true&stats.field={!cardinality=1.0}field
Can you please explain how having the same field for query and stat can
cause some issue for my better understanding of this feature?
I haven't had a chance to review the jira in depth or actaully run your
code with those configs -- but if you get a chance before i do, please
re-review the code & configs you posted and see if you can reproduce using
the *exact* same data in two different fields, and if the choice of query
makes a differnce in the behavior you see.
Will try to reproduce the same as you have mentioned and revert with
details.
Thanks,
Modassar
On Sat, Aug 22, 2015 at 3:43 AM, Chris Hostetter
wrote:
>
> : - Did you have the exact same data in both fields?
> : Both the field are string type.
>
> that's not the question i asked.
>
> is the data *in* these fields (ie: the actual value of each field for each
> document) the same for both of the fields? This is important to figuring
> out if the root problem that having docValues (or not having docValues)
> causes a problem, or is the root problem that having certain kinds of
> *data* in a string field (regardless of docValues) can cause this problem.
>
> Skimming the sample code you posted to SOLR-7954 you are definitley
> putting differnet data into "field" then you put into "field1" so it's
> still not clear what the problem is.
>
> : - Did your "real" query actually compute stats on the same field you had
> : done your main term query on?
> : I did not get the question but as much I understood and verified in the
> : Solr log the stat is computed on the field given with
> : stats.field={!cardinality=1.0}field.
>
> the question is sepcific to the example query you mentioned before and
> again in your descripion in SOLR-7954. They show that the same field
> name you are computing stats on ("field") is also used in your main query
> as a constraint on the documents ("q=field:query") which is an odd and
> very special edge case that may be pertinant to the problem you are
> seeing. Depending on what data you index, that might easily only match 1
> document -- in the case of the test code you put in jira, exactly 0
> documents since you never index the text "query" into field "field" for
> any document)
>
>
> I haven't had a chance to review the jira in depth or actaully run your
> code with those configs -- but if you get a chance before i do, please
> re-review the code & configs you posted and see if you can reproduce using
> the *exact* same data in two different fields, and if the choice of query
> makes a differnce in the behavior you see.
>
>
> :
> : Regards,
> : Modassar
> :
> : On Wed, Aug 19, 2015 at 10:24 AM, Modassar Ather >
> : wrote:
> :
> : > Ahmet/Chris! Thanks for your replies.
> : >
> : > Ahmet I think "net.agkn.hll.serialization" is used by hll() function
> : > implementation of Solr.
> : >
> : > Chris I will try to create sample data and create a jira ticket with
> : > details.
> : >
> : > Regards,
> : > Modassar
> : >
> : >
> : > On Tue, Aug 18, 2015 at 9:58 PM, Chris Hostetter <
> hossman_luc...@fucit.org
> : > > wrote:
> : >
> : >>
> : >> : > I am getting following exception for the query :
> : >> : > *q=field:query&stats=true&stats.field={!cardinality=1.0}field*.
> The
> : >> : > exception is not seen once the cardinality is set to 0.9 or less.
> : >> : > The field is *docValues enabled* and *indexed=false*. The same
> : >> exception
> : >> : > I tried to reproduce on non docValues field but could not. Please
> : >> help me
> : >> : > resolve the issue.
> : >>
> : >> Hmmm... this is a weird error ... but you haven't really given us
> enough
> : >> information to really guess what the root cause is
> : >>
> : >> - What was the datatype of the field(s)?
> : >> - Did you have the exact same data in both fields?
> : >> - Are these multivalued fields?
> : >> - Did your "real" query actually compute stats on the same field you
> had
> : >> done your main term query on?
> : >>
> : >> I know we have some tests of this bsaic siuation, and i tried to do
> ome
> : >> more manual testing to spot check, but i can't reproduce.
> : >>
> : >> If you can please provide a full copy of the data (as csv o xml or
> : >> whatever) to build your index along with all solr configs and the
> exact
> : >> queries to reproduce that would really help get to the bottom of this
> --
> : >> if you can't provide all the data, then can you at least reproduce
> with a
> : >> small set of sample data?
> : >>
> : >> either way: please file a new jira issue and attach as much detail as
> you
> : >> can -- this URL has a lot of great tips on the types of data we need
> to be
> : >> able to g
Re: Exception while using {!cardinality=1.0}.
: - Did you have the exact same data in both fields?
: Both the field are string type.
that's not the question i asked.
is the data *in* these fields (ie: the actual value of each field for each
document) the same for both of the fields? This is important to figuring
out if the root problem that having docValues (or not having docValues)
causes a problem, or is the root problem that having certain kinds of
*data* in a string field (regardless of docValues) can cause this problem.
Skimming the sample code you posted to SOLR-7954 you are definitley
putting differnet data into "field" then you put into "field1" so it's
still not clear what the problem is.
: - Did your "real" query actually compute stats on the same field you had
: done your main term query on?
: I did not get the question but as much I understood and verified in the
: Solr log the stat is computed on the field given with
: stats.field={!cardinality=1.0}field.
the question is sepcific to the example query you mentioned before and
again in your descripion in SOLR-7954. They show that the same field
name you are computing stats on ("field") is also used in your main query
as a constraint on the documents ("q=field:query") which is an odd and
very special edge case that may be pertinant to the problem you are
seeing. Depending on what data you index, that might easily only match 1
document -- in the case of the test code you put in jira, exactly 0
documents since you never index the text "query" into field "field" for
any document)
I haven't had a chance to review the jira in depth or actaully run your
code with those configs -- but if you get a chance before i do, please
re-review the code & configs you posted and see if you can reproduce using
the *exact* same data in two different fields, and if the choice of query
makes a differnce in the behavior you see.
:
: Regards,
: Modassar
:
: On Wed, Aug 19, 2015 at 10:24 AM, Modassar Ather
: wrote:
:
: > Ahmet/Chris! Thanks for your replies.
: >
: > Ahmet I think "net.agkn.hll.serialization" is used by hll() function
: > implementation of Solr.
: >
: > Chris I will try to create sample data and create a jira ticket with
: > details.
: >
: > Regards,
: > Modassar
: >
: >
: > On Tue, Aug 18, 2015 at 9:58 PM, Chris Hostetter > wrote:
: >
: >>
: >> : > I am getting following exception for the query :
: >> : > *q=field:query&stats=true&stats.field={!cardinality=1.0}field*. The
: >> : > exception is not seen once the cardinality is set to 0.9 or less.
: >> : > The field is *docValues enabled* and *indexed=false*. The same
: >> exception
: >> : > I tried to reproduce on non docValues field but could not. Please
: >> help me
: >> : > resolve the issue.
: >>
: >> Hmmm... this is a weird error ... but you haven't really given us enough
: >> information to really guess what the root cause is
: >>
: >> - What was the datatype of the field(s)?
: >> - Did you have the exact same data in both fields?
: >> - Are these multivalued fields?
: >> - Did your "real" query actually compute stats on the same field you had
: >> done your main term query on?
: >>
: >> I know we have some tests of this bsaic siuation, and i tried to do ome
: >> more manual testing to spot check, but i can't reproduce.
: >>
: >> If you can please provide a full copy of the data (as csv o xml or
: >> whatever) to build your index along with all solr configs and the exact
: >> queries to reproduce that would really help get to the bottom of this --
: >> if you can't provide all the data, then can you at least reproduce with a
: >> small set of sample data?
: >>
: >> either way: please file a new jira issue and attach as much detail as you
: >> can -- this URL has a lot of great tips on the types of data we need to be
: >> able to get to the bottom of bugs...
: >>
: >> https://wiki.apache.org/solr/UsingMailingLists
: >>
: >>
: >>
: >>
: >>
: >> : > ERROR - 2015-08-11 12:24:00.222; [core]
: >> : > org.apache.solr.common.SolrException;
: >> : > null:java.lang.ArrayIndexOutOfBoundsException: 3
: >> : > at
: >> : >
: >>
net.agkn.hll.serialization.BigEndianAscendingWordSerializer.writeWord(BigEndianAscendingWordSerializer.java:152)
: >> : > at
: >> : > net.agkn.hll.util.BitVector.getRegisterContents(BitVector.java:247)
: >> : > at net.agkn.hll.HLL.toBytes(HLL.java:917)
: >> : > at net.agkn.hll.HLL.toBytes(HLL.java:869)
: >> : > at
: >> : >
: >>
org.apache.solr.handler.component.AbstractStatsValues.getStatsValues(StatsValuesFactory.java:348)
: >> : > at
: >> : >
: >>
org.apache.solr.handler.component.StatsComponent.convertToResponse(StatsComponent.java:151)
: >> : > at
: >> : >
: >>
org.apache.solr.handler.component.StatsComponent.process(StatsComponent.java:62)
: >> : > at
: >> : >
: >>
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:255)
: >> : > at
: >> : >
: >>
org.apache.solr.handler.RequestHandl
Re: Exception while using {!cardinality=1.0}.
Hi Chris,
I have added a method in SOLR-7954 jira ticket to index sample data which
can be used to reproduce the issue.
Regards,
Modassar
On Fri, Aug 21, 2015 at 11:49 AM, Modassar Ather
wrote:
> Hi Chris,
>
> I have raised https://issues.apache.org/jira/browse/SOLR-7954 for the
> issue.
>
> - What was the datatype of the field(s)?
> The data type of fields which passes are of type string with following
> attributes.
> stored="false" omitNorms="true"/>
> The data type of the fields which fails is of type string with docvalues
> enabled and have following attributes.
> stored="false" indexed="false" docValues="true"/>
>
> - Did you have the exact same data in both fields?
> Both the field are string type.
>
> - Are these multivalued fields?
> Both the fields are multivalued.
>
> - Did your "real" query actually compute stats on the same field you had
> done your main term query on?
> I did not get the question but as much I understood and verified in the
> Solr log the stat is computed on the field given with
> stats.field={!cardinality=1.0}field.
>
> Regards,
> Modassar
>
> On Wed, Aug 19, 2015 at 10:24 AM, Modassar Ather
> wrote:
>
>> Ahmet/Chris! Thanks for your replies.
>>
>> Ahmet I think "net.agkn.hll.serialization" is used by hll() function
>> implementation of Solr.
>>
>> Chris I will try to create sample data and create a jira ticket with
>> details.
>>
>> Regards,
>> Modassar
>>
>>
>> On Tue, Aug 18, 2015 at 9:58 PM, Chris Hostetter <
>> hossman_luc...@fucit.org> wrote:
>>
>>>
>>> : > I am getting following exception for the query :
>>> : > *q=field:query&stats=true&stats.field={!cardinality=1.0}field*. The
>>> : > exception is not seen once the cardinality is set to 0.9 or less.
>>> : > The field is *docValues enabled* and *indexed=false*. The same
>>> exception
>>> : > I tried to reproduce on non docValues field but could not. Please
>>> help me
>>> : > resolve the issue.
>>>
>>> Hmmm... this is a weird error ... but you haven't really given us enough
>>> information to really guess what the root cause is
>>>
>>> - What was the datatype of the field(s)?
>>> - Did you have the exact same data in both fields?
>>> - Are these multivalued fields?
>>> - Did your "real" query actually compute stats on the same field you had
>>> done your main term query on?
>>>
>>> I know we have some tests of this bsaic siuation, and i tried to do ome
>>> more manual testing to spot check, but i can't reproduce.
>>>
>>> If you can please provide a full copy of the data (as csv o xml or
>>> whatever) to build your index along with all solr configs and the exact
>>> queries to reproduce that would really help get to the bottom of this --
>>> if you can't provide all the data, then can you at least reproduce with a
>>> small set of sample data?
>>>
>>> either way: please file a new jira issue and attach as much detail as you
>>> can -- this URL has a lot of great tips on the types of data we need to
>>> be
>>> able to get to the bottom of bugs...
>>>
>>> https://wiki.apache.org/solr/UsingMailingLists
>>>
>>>
>>>
>>>
>>>
>>> : > ERROR - 2015-08-11 12:24:00.222; [core]
>>> : > org.apache.solr.common.SolrException;
>>> : > null:java.lang.ArrayIndexOutOfBoundsException: 3
>>> : > at
>>> : >
>>> net.agkn.hll.serialization.BigEndianAscendingWordSerializer.writeWord(BigEndianAscendingWordSerializer.java:152)
>>> : > at
>>> : > net.agkn.hll.util.BitVector.getRegisterContents(BitVector.java:247)
>>> : > at net.agkn.hll.HLL.toBytes(HLL.java:917)
>>> : > at net.agkn.hll.HLL.toBytes(HLL.java:869)
>>> : > at
>>> : >
>>> org.apache.solr.handler.component.AbstractStatsValues.getStatsValues(StatsValuesFactory.java:348)
>>> : > at
>>> : >
>>> org.apache.solr.handler.component.StatsComponent.convertToResponse(StatsComponent.java:151)
>>> : > at
>>> : >
>>> org.apache.solr.handler.component.StatsComponent.process(StatsComponent.java:62)
>>> : > at
>>> : >
>>> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:255)
>>> : > at
>>> : >
>>> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)
>>> : > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2064)
>>> : > at
>>> : > org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:654)
>>> : > at
>>> org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:450)
>>> : > at
>>> : >
>>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:227)
>>> : > at
>>> : >
>>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:196)
>>> : > at
>>> : >
>>> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
>>> : > at
>>> : >
>>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
>>> : > at
>>> : >
>>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
Re: Exception while using {!cardinality=1.0}.
Hi Chris,
I have raised https://issues.apache.org/jira/browse/SOLR-7954 for the issue.
- What was the datatype of the field(s)?
The data type of fields which passes are of type string with following
attributes.
The data type of the fields which fails is of type string with docvalues
enabled and have following attributes.
- Did you have the exact same data in both fields?
Both the field are string type.
- Are these multivalued fields?
Both the fields are multivalued.
- Did your "real" query actually compute stats on the same field you had
done your main term query on?
I did not get the question but as much I understood and verified in the
Solr log the stat is computed on the field given with
stats.field={!cardinality=1.0}field.
Regards,
Modassar
On Wed, Aug 19, 2015 at 10:24 AM, Modassar Ather
wrote:
> Ahmet/Chris! Thanks for your replies.
>
> Ahmet I think "net.agkn.hll.serialization" is used by hll() function
> implementation of Solr.
>
> Chris I will try to create sample data and create a jira ticket with
> details.
>
> Regards,
> Modassar
>
>
> On Tue, Aug 18, 2015 at 9:58 PM, Chris Hostetter > wrote:
>
>>
>> : > I am getting following exception for the query :
>> : > *q=field:query&stats=true&stats.field={!cardinality=1.0}field*. The
>> : > exception is not seen once the cardinality is set to 0.9 or less.
>> : > The field is *docValues enabled* and *indexed=false*. The same
>> exception
>> : > I tried to reproduce on non docValues field but could not. Please
>> help me
>> : > resolve the issue.
>>
>> Hmmm... this is a weird error ... but you haven't really given us enough
>> information to really guess what the root cause is
>>
>> - What was the datatype of the field(s)?
>> - Did you have the exact same data in both fields?
>> - Are these multivalued fields?
>> - Did your "real" query actually compute stats on the same field you had
>> done your main term query on?
>>
>> I know we have some tests of this bsaic siuation, and i tried to do ome
>> more manual testing to spot check, but i can't reproduce.
>>
>> If you can please provide a full copy of the data (as csv o xml or
>> whatever) to build your index along with all solr configs and the exact
>> queries to reproduce that would really help get to the bottom of this --
>> if you can't provide all the data, then can you at least reproduce with a
>> small set of sample data?
>>
>> either way: please file a new jira issue and attach as much detail as you
>> can -- this URL has a lot of great tips on the types of data we need to be
>> able to get to the bottom of bugs...
>>
>> https://wiki.apache.org/solr/UsingMailingLists
>>
>>
>>
>>
>>
>> : > ERROR - 2015-08-11 12:24:00.222; [core]
>> : > org.apache.solr.common.SolrException;
>> : > null:java.lang.ArrayIndexOutOfBoundsException: 3
>> : > at
>> : >
>> net.agkn.hll.serialization.BigEndianAscendingWordSerializer.writeWord(BigEndianAscendingWordSerializer.java:152)
>> : > at
>> : > net.agkn.hll.util.BitVector.getRegisterContents(BitVector.java:247)
>> : > at net.agkn.hll.HLL.toBytes(HLL.java:917)
>> : > at net.agkn.hll.HLL.toBytes(HLL.java:869)
>> : > at
>> : >
>> org.apache.solr.handler.component.AbstractStatsValues.getStatsValues(StatsValuesFactory.java:348)
>> : > at
>> : >
>> org.apache.solr.handler.component.StatsComponent.convertToResponse(StatsComponent.java:151)
>> : > at
>> : >
>> org.apache.solr.handler.component.StatsComponent.process(StatsComponent.java:62)
>> : > at
>> : >
>> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:255)
>> : > at
>> : >
>> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)
>> : > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2064)
>> : > at
>> : > org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:654)
>> : > at
>> org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:450)
>> : > at
>> : >
>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:227)
>> : > at
>> : >
>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:196)
>> : > at
>> : >
>> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
>> : > at
>> : >
>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
>> : > at
>> : >
>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>> : > at
>> : >
>> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
>> : > at
>> : >
>> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
>> : > at
>> : >
>> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
>> : > at
>> : >
>> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
>> : > at
>> : >
>> org.eclips
Re: Exception while using {!cardinality=1.0}.
Ahmet/Chris! Thanks for your replies.
Ahmet I think "net.agkn.hll.serialization" is used by hll() function
implementation of Solr.
Chris I will try to create sample data and create a jira ticket with
details.
Regards,
Modassar
On Tue, Aug 18, 2015 at 9:58 PM, Chris Hostetter
wrote:
>
> : > I am getting following exception for the query :
> : > *q=field:query&stats=true&stats.field={!cardinality=1.0}field*. The
> : > exception is not seen once the cardinality is set to 0.9 or less.
> : > The field is *docValues enabled* and *indexed=false*. The same
> exception
> : > I tried to reproduce on non docValues field but could not. Please help
> me
> : > resolve the issue.
>
> Hmmm... this is a weird error ... but you haven't really given us enough
> information to really guess what the root cause is
>
> - What was the datatype of the field(s)?
> - Did you have the exact same data in both fields?
> - Are these multivalued fields?
> - Did your "real" query actually compute stats on the same field you had
> done your main term query on?
>
> I know we have some tests of this bsaic siuation, and i tried to do ome
> more manual testing to spot check, but i can't reproduce.
>
> If you can please provide a full copy of the data (as csv o xml or
> whatever) to build your index along with all solr configs and the exact
> queries to reproduce that would really help get to the bottom of this --
> if you can't provide all the data, then can you at least reproduce with a
> small set of sample data?
>
> either way: please file a new jira issue and attach as much detail as you
> can -- this URL has a lot of great tips on the types of data we need to be
> able to get to the bottom of bugs...
>
> https://wiki.apache.org/solr/UsingMailingLists
>
>
>
>
>
> : > ERROR - 2015-08-11 12:24:00.222; [core]
> : > org.apache.solr.common.SolrException;
> : > null:java.lang.ArrayIndexOutOfBoundsException: 3
> : > at
> : >
> net.agkn.hll.serialization.BigEndianAscendingWordSerializer.writeWord(BigEndianAscendingWordSerializer.java:152)
> : > at
> : > net.agkn.hll.util.BitVector.getRegisterContents(BitVector.java:247)
> : > at net.agkn.hll.HLL.toBytes(HLL.java:917)
> : > at net.agkn.hll.HLL.toBytes(HLL.java:869)
> : > at
> : >
> org.apache.solr.handler.component.AbstractStatsValues.getStatsValues(StatsValuesFactory.java:348)
> : > at
> : >
> org.apache.solr.handler.component.StatsComponent.convertToResponse(StatsComponent.java:151)
> : > at
> : >
> org.apache.solr.handler.component.StatsComponent.process(StatsComponent.java:62)
> : > at
> : >
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:255)
> : > at
> : >
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)
> : > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2064)
> : > at
> : > org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:654)
> : > at
> org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:450)
> : > at
> : >
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:227)
> : > at
> : >
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:196)
> : > at
> : >
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> : > at
> : >
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
> : > at
> : >
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> : > at
> : >
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
> : > at
> : >
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
> : > at
> : >
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
> : > at
> : >
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
> : > at
> : >
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> : > at
> : >
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
> : > at
> : >
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> : > at
> : >
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
> : > at
> : >
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
> : > at
> : >
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> : > at org.eclipse.jetty.server.Server.handle(Server.java:497)
> : > at
> : > org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
> : > at
> : >
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
> : > at
> : >
> org.eclipse.jetty.io.AbstractConnecti
Re: Exception while using {!cardinality=1.0}.
: > I am getting following exception for the query :
: > *q=field:query&stats=true&stats.field={!cardinality=1.0}field*. The
: > exception is not seen once the cardinality is set to 0.9 or less.
: > The field is *docValues enabled* and *indexed=false*. The same exception
: > I tried to reproduce on non docValues field but could not. Please help me
: > resolve the issue.
Hmmm... this is a weird error ... but you haven't really given us enough
information to really guess what the root cause is
- What was the datatype of the field(s)?
- Did you have the exact same data in both fields?
- Are these multivalued fields?
- Did your "real" query actually compute stats on the same field you had
done your main term query on?
I know we have some tests of this bsaic siuation, and i tried to do ome
more manual testing to spot check, but i can't reproduce.
If you can please provide a full copy of the data (as csv o xml or
whatever) to build your index along with all solr configs and the exact
queries to reproduce that would really help get to the bottom of this --
if you can't provide all the data, then can you at least reproduce with a
small set of sample data?
either way: please file a new jira issue and attach as much detail as you
can -- this URL has a lot of great tips on the types of data we need to be
able to get to the bottom of bugs...
https://wiki.apache.org/solr/UsingMailingLists
: > ERROR - 2015-08-11 12:24:00.222; [core]
: > org.apache.solr.common.SolrException;
: > null:java.lang.ArrayIndexOutOfBoundsException: 3
: > at
: >
net.agkn.hll.serialization.BigEndianAscendingWordSerializer.writeWord(BigEndianAscendingWordSerializer.java:152)
: > at
: > net.agkn.hll.util.BitVector.getRegisterContents(BitVector.java:247)
: > at net.agkn.hll.HLL.toBytes(HLL.java:917)
: > at net.agkn.hll.HLL.toBytes(HLL.java:869)
: > at
: >
org.apache.solr.handler.component.AbstractStatsValues.getStatsValues(StatsValuesFactory.java:348)
: > at
: >
org.apache.solr.handler.component.StatsComponent.convertToResponse(StatsComponent.java:151)
: > at
: >
org.apache.solr.handler.component.StatsComponent.process(StatsComponent.java:62)
: > at
: >
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:255)
: > at
: >
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)
: > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2064)
: > at
: > org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:654)
: > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:450)
: > at
: >
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:227)
: > at
: >
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:196)
: > at
: >
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
: > at
: > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
: > at
: >
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
: > at
: > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
: > at
: >
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
: > at
: >
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
: > at
: > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
: > at
: >
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
: > at
: >
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
: > at
: >
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
: > at
: >
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
: > at
: >
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
: > at
: >
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
: > at org.eclipse.jetty.server.Server.handle(Server.java:497)
: > at
: > org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
: > at
: > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
: > at
: > org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
: > at
: >
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
: > at
: >
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
: > at java.lang.Thread.run(Thread.java:745)
: >
: > Kindly let me know if I need to ask this on any of the related jira issue.
: >
: > Thanks,
: > Modassar
: >
:
-Hoss
http://www.lucidworks.com/
Re: Exception while using {!cardinality=1.0}.
Hi Modassar,
What is this "net.agkn.hll.serialization" ? Custom plugin or something?
Ahmet
On Tuesday, August 18, 2015 9:23 AM, Modassar Ather
wrote:
Any suggestions please.
Regards,
Modassar
On Thu, Aug 13, 2015 at 4:25 PM, Modassar Ather
wrote:
> Hi,
>
> I am getting following exception for the query :
> *q=field:query&stats=true&stats.field={!cardinality=1.0}field*. The
> exception is not seen once the cardinality is set to 0.9 or less.
> The field is *docValues enabled* and *indexed=false*. The same exception
> I tried to reproduce on non docValues field but could not. Please help me
> resolve the issue.
>
> ERROR - 2015-08-11 12:24:00.222; [core]
> org.apache.solr.common.SolrException;
> null:java.lang.ArrayIndexOutOfBoundsException: 3
> at
> net.agkn.hll.serialization.BigEndianAscendingWordSerializer.writeWord(BigEndianAscendingWordSerializer.java:152)
> at
> net.agkn.hll.util.BitVector.getRegisterContents(BitVector.java:247)
> at net.agkn.hll.HLL.toBytes(HLL.java:917)
> at net.agkn.hll.HLL.toBytes(HLL.java:869)
> at
> org.apache.solr.handler.component.AbstractStatsValues.getStatsValues(StatsValuesFactory.java:348)
> at
> org.apache.solr.handler.component.StatsComponent.convertToResponse(StatsComponent.java:151)
> at
> org.apache.solr.handler.component.StatsComponent.process(StatsComponent.java:62)
> at
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:255)
> at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)
> at org.apache.solr.core.SolrCore.execute(SolrCore.java:2064)
> at
> org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:654)
> at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:450)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:227)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:196)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:497)
> at
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
> at
> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
>
> Kindly let me know if I need to ask this on any of the related jira issue.
>
> Thanks,
> Modassar
>
Re: Exception while using {!cardinality=1.0}.
Any suggestions please.
Regards,
Modassar
On Thu, Aug 13, 2015 at 4:25 PM, Modassar Ather
wrote:
> Hi,
>
> I am getting following exception for the query :
> *q=field:query&stats=true&stats.field={!cardinality=1.0}field*. The
> exception is not seen once the cardinality is set to 0.9 or less.
> The field is *docValues enabled* and *indexed=false*. The same exception
> I tried to reproduce on non docValues field but could not. Please help me
> resolve the issue.
>
> ERROR - 2015-08-11 12:24:00.222; [core]
> org.apache.solr.common.SolrException;
> null:java.lang.ArrayIndexOutOfBoundsException: 3
> at
> net.agkn.hll.serialization.BigEndianAscendingWordSerializer.writeWord(BigEndianAscendingWordSerializer.java:152)
> at
> net.agkn.hll.util.BitVector.getRegisterContents(BitVector.java:247)
> at net.agkn.hll.HLL.toBytes(HLL.java:917)
> at net.agkn.hll.HLL.toBytes(HLL.java:869)
> at
> org.apache.solr.handler.component.AbstractStatsValues.getStatsValues(StatsValuesFactory.java:348)
> at
> org.apache.solr.handler.component.StatsComponent.convertToResponse(StatsComponent.java:151)
> at
> org.apache.solr.handler.component.StatsComponent.process(StatsComponent.java:62)
> at
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:255)
> at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143)
> at org.apache.solr.core.SolrCore.execute(SolrCore.java:2064)
> at
> org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:654)
> at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:450)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:227)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:196)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:497)
> at
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
> at
> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
>
> Kindly let me know if I need to ask this on any of the related jira issue.
>
> Thanks,
> Modassar
>
