On 26/08/15 18:05, Erick Erickson wrote:
> bq: my dog
> has fleas
> I wouldn't want some variant of "og ha" to match,
>
> Here's where the mysterious "positionIncrementGap" comes in. If you
> make this field "multiValued", and index this like this:
>
> my dog
> has fleas
>
>
> then the positi
the additional \R tokenizer in the index chain
because the the document can be multiple lines (but the search text is
always a single line) and if the document was
my dog
has fleas
I wouldn't want some variant of "og ha" to match, but I didn't realize
it didn't give me any
Hi
I'm trying to build an index for technical documents that basically
works like "grep", i.e. the user gives an arbitray substring somewhere
in a line of a document and the exact matches will be returned. I
specifically want no stemming etc. and keep all whitespace, parentheses
etc. because they
On 11/12/13 5:20 PM, Shawn Heisey wrote:
> Ensure that all handler names start with a slash character, so they are
> things like "/query", "/select", and so on. Make sure that handleSelect
> is set to false on your requestDispatcher config. This is how Solr 4.x
> examples are set up already.
>
>
Christian
>
> Best,
> Erick
>
>
> On Tue, Nov 12, 2013 at 7:09 AM, Christian Ramseyer wrote:
>
>> Hi guys
>>
>> I'm prototyping a multi-tenant search. I have various document sources and
>> a tenant can potentially access subsets of a
Hi guys
I'm prototyping a multi-tenant search. I have various document sources and a
tenant can potentially access subsets of any source.
Also tenants have overlapping access to the sources, why I'm trying to do it in
a single core.
I'm doing this by labeling the source (origin, single value)
