ah, thanks for the link.
--
John Blythe
On Wed, Oct 4, 2017 at 9:23 AM, Erick Erickson
wrote:
> Check. The problem is they don't encode the exact length. I _think_
> this patch shows you'd be OK with shorter lengths, but check:
> https://issues.apache.org/jira/browse/LUCENE-7730.
>
> Note it's
Check. The problem is they don't encode the exact length. I _think_
this patch shows you'd be OK with shorter lengths, but check:
https://issues.apache.org/jira/browse/LUCENE-7730.
Note it's not the patch that counts here, just look at the table of lengths.
Best,
Erick
On Wed, Oct 4, 2017 at 4:2
interesting idea.
the field in question is one that can have a good deal of stray zeros based
on distributor skus for a product and bad entries from those entering them.
part of the matching logic for some operations look for these discrepancies
by having a simple regex that removes zeroes. so 400
Are the norms a good approximation for you ?
If you preserve norms at indexing time ( it is a configuration that you can
operate in the schema.xml) you can retrieve them with this specific function
query :
*norm(field)*
Returns the "norm" stored in the index for the specified field. This is the
pr
I’d personally use your second option. Simple and straightforward if you can
afford the time for a reindex
> On Oct 3, 2017, at 6:23 PM, John Blythe wrote:
>
> hey all.
>
> was hoping to find a query function that would allow me to filter based on
> the length of an indexed value. only things
