Lots of discussion about XY problems on this list lately. Maybe I'm a
bit guilty. :D
I used the example from the docs to be clear, but our real use case is
indexing file metadata on a large filesystem. With a few fields like owner,
group, mode, lastmodified, filesize, type, and path, the path
A couple of things.
bq. the field is by far the largest contributor to the index size already,
That's a rather odd statement. It implies that there's very little
else in your documents. If you have any descriptions etc. I'd think
that the category info wouldn't be all that huge in comparison. How
Hi,
we've recently changed our Solr-Version from 6.2.1 to 7.5.0, and since then,
whenever we execute a query on solr, a new thread is being created and never
closed.
These threads are all labelled "Connection evictor" and the gather until a
critical mass is reached and either the OS cannot cre
Hi,
A customer will use Streaming with VERY LARGE epxressions since they embed
super long query strings in 'search()' part of the expression. Now I was under
the impression that this would always be a POST, but now we get the following
exception when reading the TupleStream which includes in th
Hi,
I have a schema that has a descendent_path field as configured in the
PathTokenizerHierarchyFactory docs:
Using the example in the docs: *For example, in the configuration below a
query for Books/NonFic will match documents indexed with values like
Books/Non
Thanks Mikhail,
I will check this FieldMaskingSpanQuery out.
Thanks
Melchi
On Fri, 23 Nov 2018 at 19:17, Mikhail Khludnev wrote:
>
> There's no way to search with positions across other fields. I can only
> recommend to prepend prefix terms to distinguish them.
> But hold on, what about FieldMas
Hi Alex,
Thanks for your reply. I am keeping the original with the edge, but not
sure how to mark them as original. I would like to avoid a prefix match
for the full words.
You mentioned post-filter - can you shed some light on this?. If only I
can remove these over-matches, that would be great
Thanks Erick for your inputs,
Yes, i was indeed looking for this. I was little worried about the *
expansion. As it is already part of a large query. But this sounds like
the simplest way I can achieve this for now.
If I indeed slows down, will revisit this.
Was wondering if some how I can cre
There's no way to search with positions across other fields. I can only
recommend to prepend prefix terms to distinguish them.
But hold on, what about FieldMaskingSpanQuery? It's available in
XMLQparser, you may try.
On Fri, Nov 23, 2018 at 3:37 AM NewMelchizedec sundararaj
wrote:
> Hi Fellow Se
It make sense to have docValues=true for _root_ for uniqueBlock()
On Thu, Nov 22, 2018 at 6:44 PM Vincenzo D'Amore wrote:
> Hi guys, this is an interesting thread.
>
> Looking at schema.xml I found having uniqueKey (type="string") configured
> as docValues="true" but, I also found that _root_ is
It is not clear how much flexibility you expect in those queries. Can
the second word never be full name? Can there be more than 2 words?
How do you know the length of the prefix? When you say prefix, do you
mean 'jo' is expected to match 'joseph'?
So, just generically, I would say why not index e
11 matches
Mail list logo
