Re: Solr schema design: fitting time-series data

2017-01-17 Thread map reduced
That's a good point Alex, about indexed vs stored. Since all my queries are exact match, I can just have them stored=false to save space. I believe that helps since there are billions of rows and it'll hopefully save on quite some of space. But nothing can be done for squeezing dates in same docume

Re: Solr schema design: fitting time-series data

2017-01-17 Thread Alexandre Rafalovitch
On 16 January 2017 at 00:54, map reduced wrote: > some way to squeeze timestamps in single > document so that it doesn't increase the number of document by a lot and I > am still able to range query on 'ts'. Would DateRangeField be useful here? https://cwiki.apache.org/confluence/display/solr/Wor

Re: Solr schema design: fitting time-series data

2017-01-17 Thread map reduced
Anyone has any idea? On Sun, Jan 15, 2017 at 9:54 PM, map reduced wrote: > I may have used wrong terminology, by complex types I meant non-primitive > types. Mutlivalued can be conceptualized as a list of values for instance > in your example myint = [ 32, 77] etc which you can possibly analyze

Re: Solr schema design: fitting time-series data

2017-01-15 Thread map reduced
I may have used wrong terminology, by complex types I meant non-primitive types. Mutlivalued can be conceptualized as a list of values for instance in your example myint = [ 32, 77] etc which you can possibly analyze and query upon. What I was trying to ask is if a complex type can be multi-valued

Re: Solr schema design: fitting time-series data

2017-01-15 Thread Erick Erickson
bq: I know multivalued fields don't support complex data types Not sure what you're talking about here. mulitValued actually has nothing to do with data types. You can have text fields which are analyzed and produce multiple tokens and are multiValued. You can have primitive types (string, int/lo