user@lucene.apache.org
> Sent: Monday, May 18, 2015 12:00:37 PM
> Subject: Re: Problem with solr.LengthFilterFactory
>
> Sorry for not spotting that earlier. Lucene itself does have such a limit.
> No way around it - an individual term is limited to 32K-2 bytes. Lucene is
> designed for
. More custom
code.
Thanks everyone for your help.
Charles
- Original Message -
From: "Jack Krupansky"
To: solr-user@lucene.apache.org
Sent: Monday, May 18, 2015 12:00:37 PM
Subject: Re: Problem with solr.LengthFilterFactory
Sorry for not spotting that earlier. Lucene i
7;m afraid my understanding is not complete. Can you fill in the gaps?
>
> Thanks,
> Charles
>
>
> - Original Message -
>
> From: "Jack Krupansky"
> To: solr-user@lucene.apache.org
> Sent: Friday, May 15, 2015 4:31:22 PM
> Subject: Re: Problem wit
y understanding is not complete. Can you fill in the gaps?
Thanks,
Charles
- Original Message -
From: "Jack Krupansky"
To: solr-user@lucene.apache.org
Sent: Friday, May 15, 2015 4:31:22 PM
Subject: Re: Problem with solr.LengthFilterFactory
Sorry that my brain has tu
456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890"
],
"_ve
90",
> "parsedquery":
> "portal_package:1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456
> portal_package:789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678
On 5/15/2015 2:06 PM, Charles Sanders wrote:
> I have deleted all records from my index. Stopped solr. Made the schema
> changes as requested. Started solr. Then insert the one test record. Then
> search. Still see the same results. No portal_package is not the unique key,
> its uri. Which is a
34567890123456789012345678901234567890123456789012345678901234567890123456
portal_package:7890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890",
"parsedquery_toString":
"portal_package:123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789
On 5/15/2015 1:23 PM, Shawn Heisey wrote:
> Then I looked back at your fieldType definition and noticed that you
> are only defining an index analyzer. Remove the 'type="index"' part of
> the analyzer config so it happens at both index and query time,
> reindex, then try again.
The reindex may be
On 5/15/2015 12:47 PM, Charles Sanders wrote:
> Ran the same test as below. Added echoParams=all and debug=query. Thanks for
> the help!
Initially, I was a little confused by something I saw in your debug
output. I've broken up the query text with newlines into 50 character
increments for clari
345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345
portal_package:678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901
On 5/15/2015 10:04 AM, Charles Sanders wrote:
> Agree 100%. The value returned is the value stored. Not affected by the
> analyzer.
>
> However, I searched for that token. See my query? I would expect the analyzer
> to remove the large token. So that when I search for the large token I would
>
missing something here?
- Original Message -
From: "Jack Krupansky"
To: solr-user@lucene.apache.org
Sent: Friday, May 15, 2015 11:56:51 AM
Subject: Re: Problem with solr.LengthFilterFactory
The returned value is the stored or original source value - only the
indexed terms ar
nd": 1,
> "start": 0,
> "docs": [
> {
> "documentKind": "test",
> "uri": "test300",
> "id": "test300",
> "portal_package": [
>
> "12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678
3456789012345678901234567890123456789012345678901234567890"
],
"_version_": 1501249997589446700,
"timestamp": "2015-05-15T15:26:05.205Z",
"language": "en"
}
]
}
}
- Original Message -
From: "Shawn Heisey"
To: so
On 5/15/2015 8:49 AM, Charles Sanders wrote:
> I'm seeing a problem with the LengthFilter. It appears to work fine until I
> increase the max value above 254. At the point it stops removing the very
> large token from the stream. As a result I get the error:
> java.lang.IllegalArgumentException:
I'm seeing a problem with the LengthFilter. It appears to work fine until I
increase the max value above 254. At the point it stops removing the very large
token from the stream. As a result I get the error:
java.lang.IllegalArgumentException: Document contains at least one immense
term.. U
17 matches
Mail list logo
