With _source as false , all your visualization other than table should work
just fine.
But then table visualization needs _source to work fine as it CANT recreate
the data from inverted index.
Interesting.. Do you know if it's possible to provide the source for the
table from another provider?
I guess I could build it if totally necessary.
But without the table is probably fine for now.. I might actually store
some content there now that I think about it. Maybe a title, link, and
summary.
On Saturday, October 4, 2014 8:31:34 PM UTC-7, vineeth mohan wrote:
Hello Kevin ,
With _source as false , all your visualization other than table should
work just fine.
But then table visualization needs _source to work fine as it CANT
recreate the data from inverted index.
Thanks
Vineeth
On Sun, Oct 5, 2014 at 4:21 AM, Kevin Burton <burto...@gmail.com
<javascript:>> wrote:
Lucene supports the ability for a field to not be stored inline with the
content. It only stores the inverted index if stored=false.
Right now all our content is stored in Cassandra. What I want to do is
also write it to ES and only have it store the inverted index.
Otherwise, I'm writing content twice... the inverted index will only take
about 40% of the original content.
I imagine ES can do this... Solr can.. but I'm having trouble determining
if ES can as well.
How would Kibana operate in this situation? I would want it to be able
to show the content ... will Kibana break in this situation?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.