Wait? You are trying to clean up text just before indexing? Have you tried
an UpdateRequestProcessor to do that?
Regards,
Alex
On 1 Jan 2016 1:14 am, "Zheng Lin Edwin Yeo" wrote:
> Yes, I tried using the latest post.jar, and I got the same error.
>
> I have shortlisted the problem down to th
Is there any interest in this? While i think it's important and inline
with faceting available in the new json facet api, I've seen no discussion
on it so I'm wondering if it's best I add support for this using a custom
facet component even though the majority of the component will be a copy
which
Yes, I'm trying to clean up the text before indexing, but I have not tried
on UpdateRequestProcessor. I have been modifying the SolrContentHandler to
do that.
Regards,
Edwin
On 1 January 2016 at 16:32, Alexandre Rafalovitch
wrote:
> Wait? You are trying to clean up text just before indexing? Ha
Hi
in the reference guide about language analysis you can find an example
where docvalues are used in combination with the solr.ICUCollationField type
...
...
But the documentation about docvalues itself
https://cwiki.apache.org/confluence/display/solr/DocValues
says you can only use
On Mon, Dec 28, 2015 at 9:11 AM, Joel Bernstein wrote:
> In
> order to join result sets you would typically need to be working with the
> entire result sets from both sides of the join, which may be too slow
> without the /export handler.
We now have https://issues.apache.org/jira/browse/SOLR-822
Thanks.. I upgraded java to latest 1.7 version. Removed all docs from index
by deleting directory & re-indexed it again.
Solr is not crashing anymore.
--
View this message in context:
http://lucene.472066.n3.nabble.com/JVM-error-v-StubRoutines-jbyte-disjoint-arraycopy-tp4244603p4248152.html
Se
On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
> We are getting weird results with if(exists(a),b,c). We are getting b+c!!
>
> http://localhost:8983/solr/providersearch/select?q=*:*&wt=json&state=state:%22CO%22&state1=state:%22NY%22&fq=if(exists(query($state1)),{!lucene%20v=$state1},{!lu
Sure.
If the state:NY returns results filter by state:NY, if it does not, then
use state:CO. If we have results in NY, use it, otherwise use CO.
OK?
On Fri, Jan 1, 2016 at 1:15 PM, Upayavira wrote:
>
>
> On Thu, Dec 31, 2015, at 11:50 PM, William Bell wrote:
> > We are getting weird results wi
Example.
http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!lucene%20v=$state1}
This return 236,000
http://localhost:8983/solr/providersearch/select?wt=json&state=state:%22CO%22&state1=state:%22NY%22&fl=ss,score&q=*:*&fq={!l
Another weirdness:
http://localhost:8983/solr/providersearch/select?wt=json&state=state:CO&state1=state:NY&fl=*&q=*:*&tt=$state1&fq={!lucene%20v=$tt}
That does not return anything.
But if I set v=$state1 I get results.
Can I not set equivalent variables?
On Fri, Jan 1, 2016 at 2:07 PM, Willi
I'm afraid I cannot see how this can be done - at least without coding.
Basically, when your filter is being evaluated, you want to make use of
knowledge of the main query - for normal queries, that isn't possible,
as they are created independently.
You could use potentially use a "post filter" i
This all started with me trying to use {!switch} to indicate with CO or NY
to use. if we pass state1, that is supposed to take precedence, but if
nothing is returned, then use state Make sense now?
I could not find a way to check for strlen($state1). Which is what I want
in the case statement.
Maybe we can add function value on a switch?
fq={!switch case.gt.0
default=$state
func=len($state1)}
We could add: gt, lt, eq, ge, le ?
gt: greater than
lt: less than
eq: equal
ge: greater than or equal
le: less than or equal
??
On
Forgot last bit:
fq={!switch case.gt.0=$state1
default=$state
func=len($state1)}
On Fri, Jan 1, 2016 at 2:39 PM, William Bell wrote:
> Maybe we can add function value on a switch?
>
> fq={!switch case.gt.0
>
Also ne: not equal.
This is like KSH.
On Fri, Jan 1, 2016 at 2:40 PM, William Bell wrote:
> Forgot last bit:
>
> fq={!switch case.gt.0=$state1
> default=$state
> func=len($state1)}
>
>
> On Fri, Jan 1, 2016 at 2:39 PM, William Bell wrot
You've got to think of what the queries will be that you produce under
the bonnet - what you are talking about is either a (!func} or a
{!frange} query - both of which are inefficient as they must scan the
entire resultset.
However, what you're trying to do is evaluate the length of the *input
val
Sample code for a simple query parser?
On Fri, Jan 1, 2016 at 3:08 PM, Upayavira wrote:
> You've got to think of what the queries will be that you produce under
> the bonnet - what you are talking about is either a (!func} or a
> {!frange} query - both of which are inefficient as they must scan
On 12/31/2015 8:03 PM, Zheng Lin Edwin Yeo wrote:
> But the problem I'm facing now is that during optimizing, the memory usage
> of the server hit the maximum of 64GB, and I believe the optimization could
> not be completed fully as there is not enough memory, so when I check the
> index again, it
18 matches
Mail list logo
