Using doc fields streamable facility

I have a use case where I need to append certain amount of text to an
existing field of the document which has been already indexed earlier.
After appending I will be reindexing the document. I am predicting the
amount of data which is going to be stored in that single field of my
document will be pretty large so I decided not to store the field as well
as disabled the _source feature on that document type.

I also feel as there will be several indexing/reindexing operations will be
going on simultaneously in the JVM (I am currently using Java API), it will
be highly memory inefficient to bring all such long string object.

I am wondering if the '*streamability' *the field in document in Java API
can be used in someway to make my use case memory efficient. I yes, I would
like to see a kind of pseudocode or example for steps stream operations to
follow to achieve the whole use case memory efficiently?

--

If the field is not stored and source is disabled, then there is nothing to
go on. No data to append to.

Even if things are stored, updating Lucene (and therefore ElasticSearch) is
a well known issue. ElasticSearch can get around it by using the update
API, which is essentially a re-indexing on the server side, but it still
revolves around the Lucene storage format.

--
Ivan

On Fri, Nov 9, 2012 at 12:19 AM, Atharva Patel patelatharva@gmail.comwrote:

I have a use case where I need to append certain amount of text to an
existing field of the document which has been already indexed earlier.
After appending I will be reindexing the document. I am predicting the
amount of data which is going to be stored in that single field of my
document will be pretty large so I decided not to store the field as well
as disabled the _source feature on that document type.

I also feel as there will be several indexing/reindexing operations will
be going on simultaneously in the JVM (I am currently using Java API), it
will be highly memory inefficient to bring all such long string object.

I am wondering if the '*streamability' *the field in document in Java API
can be used in someway to make my use case memory efficient. I yes, I would
like to see a kind of pseudocode or example for steps stream operations to
follow to achieve the whole use case memory efficiently?

--

--