That is certainly possible, just open an issue for that.
-shay.banon
On Thu, Mar 18, 2010 at 12:45 AM, Sergio Bossa sergio.bossa@gmail.comwrote:
Shay, what about implementing a pluggable API to externally lookup the
document?Sergio Bossa
Sent by iPhoneIl giorno 17/mar/2010, alle ore 23.35, Shay Banon <
shay.banon@elasticsearch.com> ha scritto:Couldn't agree more. In terms of usability, the aim of elasticsearch is to
be the best solution out of the box, and the most configurable one when
needed. Its really up to the users.As a side note, let me explain why storing the source field might make
sense in certain features. Lets say I want to expose an API that allows to
reindex an index into a new index. If elasticsearch has the source
documents, then this API can be implemented easily within elasticsearch. If
the source is not there, then elasticsearch can't really provide this API,
and the user would need to "refetch" the data from another data store, and
index it. The simplicity of the first solution is something that I really
like, but the user can choose. If source is not enabled, then the API will
simply bail.There are other cases where it would be nice to have the actual content of
a field (and not its analyzed form) without the user having to explicitly
"store" it. But most of them are solved by the user cherry picking which
fields to store.-shay.banon
On Thu, Mar 18, 2010 at 12:16 AM, Eric Gaumer < egaumer@gmail.com
egaumer@gmail.com> wrote:On Wed, Mar 17, 2010 at 5:58 PM, Shay Banon <shay.banon@elasticsearch.com
shay.banon@elasticsearch.com> wrote:Not sure that I agree regarding the higher throughput argument, but, in
any case, its there for people to use it :).In all fairness, search (typically) returns references to actual resources
(look at Google). With this in mind, Sergio's argument is a valid one. One
of the common pitfalls of enterprise search projects is that folks want to
use the search index to house complete documents. This has many drawbacks
especially with regards to volatile data. Of course, the tight integration
between terrastore and elasticsearch invalidate some of the concerns.With that said, I really like how elasticsearch emulates a (searchable)
key/value store by returning the entire document. I think it expands the
possibilities for different use cases. I've actually used it as a full
fledged data store for customer information that (until recently) was housed
in a large unwieldy spreadsheet.The ability to disable this feature means users can decide what makes the
most sense for their particular use case.Regards,
-Eric