[
https://issues.apache.org/jira/browse/SOLR-10708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-10708.
-----------------------------------
Resolution: Invalid
Blast, got fooled again by Chrome attempting to prettify XML or JSON. I vaguely
remember someone saying something about this a while ago being a javascript (?)
issue. Sure wish I'd remembered this a few hours earlier.
Anyway, I issue a query q=id:some_id and Chrome displays:
facet_d: 7542527836020716000
Do the same thing via curl or Safari (which doesn't have a prettify plugin
installed) and I get:
facet_d:7542527836020715275
Of course I cut/pasted the Chrome value in when I was trying to find documents
with specific values for facet_d and failed.
Which explains why every time I thought I had a failing test I eventually found
out it was a test problem, not a Solr/Lucene problem. And why having a range
"wide enough" would work.
[~dsmiley][~jpountz] you can relax now.
> Cannot find certain long values when docValues=true,indexed=false
> -----------------------------------------------------------------
>
> Key: SOLR-10708
> URL: https://issues.apache.org/jira/browse/SOLR-10708
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 6.7
> Reporter: Erick Erickson
>
> I define a field like this:
> <field indexed="false" name="facet_d" stored="false" type="tlong"
> docValues="true"/>
> When I index these with a program assigning random longs to the fields
> searching on facet_d fails to find some values, but _only_ when there are
> multiple documents. For instance, the value "6850281131226296000" was in this
> field, but searching on facet_d:6850281131226296000 does not find the
> document.
> Searching on facet_d:[6850281131226290000 TO 6850281131226297000] works if
> the range is "wide enough", but I don't have a good sense of how wide that
> is. Note that the values in that clause are not identical!
> NOTE: this problem does _not_ occur if there's only one document in the
> corpus. I'll try to make a failing test.
> [~jpountz] suggested that I look at the actual indexed values, but since the
> document is found in the single-doc case I'll assume that the stored
> compatibly between the index and query at least.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
