Hi Uwe,
thanks for the talk suggestion(s)*.
I was using it for faster term lookups of a long 'id'. How would this be
done with 4.0? Before I did it via Term:
new Term(fieldName, NumericUtils.longToPrefixCoded(longValue));
How should I generally do "term lookup" in 4.0 as you said in the video
t
BTW: how can I use NumericUtils.longToPrefixCoded in 4.0 ?
Peter.
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
> I assume it was a bug like noted before?
Exactly. Nothing to do with Lucene IMHO
Peter.
--
http://jetsli.de news reader for geeks
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-
Hi,
I was hitting a similar exception (for me it was of type 'long'). But I
thought it was because I had a programming mistake. termAtt is reused.
Couldn't it be that when two threads accessing the incrementToken method
at the same time that problems occur?
This exception disappeared when I fixed
Hi Lukáš, hi Mark
> https://issues.apache.org/jira/browse/SOLR-839
thanks for pointing me there
> > although some parameters are available as URL parameters as well in ES
> Not sure if I understood exactly what you meant here but do you know you
> can always use "source" URL parameter to p
> I don't think it's possible.
Eh, of course its possible (if I would understand it I would do it. no,
no, just joking ;))
and yes, Solr its a shorter for some common use cases. I don't think
that there is a 'best', but JSON can map 1:1 to lucene.
The biggest problem with ES's syntax is that
>> : "Think of the Query DSL as an AST of queries"
>> : http://www.elasticsearch.org/guide/reference/query-dsl/
>>
>> I'm not familiar with ES, but FWIW: based on that one page the "Query DSL"
>> doesn't really sound much more powerful then what you can do with nested
>> queries, local params, and
>> even high complexity as ES supports lucene-like query nesting via JSON
> That sounds interesting. Where is it described in the ES docs? Thanks.
"Think of the Query DSL as an AST of queries"
http://www.elasticsearch.org/guide/reference/query-dsl/
For further info ask on ES mailing list.
Reg
Hi,
its not really fair to compare NRT of Solr to ElasticSearch.
ElasticSearch provides NRT for distributed indices as well... also when
doing heavy indexing Solr lacks real NRT.
The only main disadvantages of ElasticSearch are:
* only one (main) committer
* no autowarming
> the ES team in t
well using embedded solr would be an option althought not recommended.
or look into elasticsearch:
http://www.elasticsearch.org/guide/reference/index-modules/analysis/phonetic-tokenfilter.html
http://www.elasticsearch.org/guide/reference/java-api/client.html
Regards,
Peter.
> Can I use Solr as
10 matches
Mail list logo
