As it says in the title, we are moving from 3.0.2 from to 3.4. I am interested
in issues about the need to build a new index or just keep changing the current
one. My company has been busy building software and have not upgraded the
Lucene and Tika libraries since last year, but I'm trying to
Hi Uwe,
I ran my setup with JDK1.6.0_29 .
Exception that I get -
2011-11-15 23:54:24,518 [MC:10.10.176.148-1321429549689-426 FS:emag_393219_0]
ERROR indexer - MergeWithFiler: MC: 393219, shard 0, guid
10.10.176.148-1321429549689-426: Error in addIndex()/kazMaybeMerge():
/sideline/fs_393219/ca
: "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 param refs usin
The docs are slim on examples.
On Wed, Nov 16, 2011 at 3:35 PM, Peter Karich wrote:
>
>>> 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://w
>> 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
> even high complexity as ES supports lucene-like query nesting via JSON
That sounds interesting. Where is it described in the ES docs? Thanks.
On Wed, Nov 16, 2011 at 1:36 PM, Peter Karich wrote:
> Hi,
>
> its not really fair to compare NRT of Solr to ElasticSearch.
> ElasticSearch provides
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
I am currently working on a refactoring of FSTLookup so that either one or
both of your objectives will be possible.
I would still argue that storing exact scores does not make much sense
(think: if you collect query logs then you probably won't differentiate
between two suggestions that differ by
Hi
I am trying to implement an auto complete suggest system using FST.
For my use case I cannot use FSTLookup for the following reasons.
1. I cannot construct the display string using the arc labels like
FSTLookup as the display strings for autocompletion are different from the
strings used as pr
On Wed, Nov 16, 2011 at 10:36 AM, Shashi Kant wrote:
> I had posted this earlier on this list, hope this provides some answers
>
> http://engineering.socialcast.com/2011/05/realtime-search-solr-vs-elasticsearch/
Except it's an out of date comparison.
We have NRT (near real time search) in Solr no
I had posted this earlier on this list, hope this provides some answers
http://engineering.socialcast.com/2011/05/realtime-search-solr-vs-elasticsearch/
On Wed, Nov 16, 2011 at 9:53 AM, Federico Fissore wrote:
> Peyman Faratin, il 16/11/2011 15:12, ha scritto:
>
> Hi
>>
>> A client is conside
Peyman Faratin, il 16/11/2011 15:12, ha scritto:
Hi
A client is considering moving from Lucene to ElasticSearch. What is the
community's opinion on ES?
thank you
we have recently compared ES to Solr to estimate the effort of evolving
our search infrastructure (it was game like: two teams t
Under the covers, ElasticSearch contains mutliple lucene indexes -- so the
full expressiveness of lucene queries are translatable to ElasticSearch --
but the benefit of using ES as an abstraction layer to give sharded
searches is something attractive enough that we're looking at it too. ;)
We typ
Hi
A client is considering moving from Lucene to ElasticSearch. What is the
community's opinion on ES?
thank you
Peyman
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-use
14 matches
Mail list logo