Re: Dynamic fields vs parent child

2017-06-28 Thread Rick Leir
Saurabh Maybe you need two fields. The first field is named "keyName" and the second is "keyValue". Give that a try, though searching with AND may be a challenge. Otherwise, use one field named "whatever" containing "key-value", assuming '-' never appears in keys or values. Search for an exa

Re: Dynamic fields vs parent child

2017-06-27 Thread Susheel Kumar
Do you have any close count of how many max dynamic fields you may have (1k, 2k or 3k etc.). In one of our index we have a total around 2K dynamic fields across all documents. My suggestion would be to try out dynamic fields for the use case you are describing and do some real performance test. T

Re: Dynamic fields vs parent child

2017-06-27 Thread Saurabh Sethi
We have key-value pairs that need to be searchable. We are looking for best approach, both in terms of indexing (fast as well as space efficient) as well as retrieval (fast search). Right now, the two approaches that we have are: Nested docs or dynamic fields (myField_*_time:some date) The number

Re: Dynamic fields vs parent child

2017-06-27 Thread Susheel Kumar
Can you describe your use case in terms of what business functionality you are looking to achieve. Thanks, Susheel On Mon, Jun 26, 2017 at 4:26 PM, Saurabh Sethi wrote: > Number of dynamic fields will be in thousands (millions of users + > thousands of events shared between subsets of users). >

Re: Dynamic fields vs parent child

2017-06-26 Thread Saurabh Sethi
Number of dynamic fields will be in thousands (millions of users + thousands of events shared between subsets of users). We also thought about indexing in one field with value being fieldname_fieldvalue. Since we support range queries for dates and numbers, it won't work out of box. On Mon, Jun 2

Re: Dynamic fields vs parent child

2017-06-26 Thread Erick Erickson
How many distinct fields do you expect across _all_ documents? That is, if doc1 has 10 dynamic fields and doc2 has 10 dynamic fields, will there be exactly 10 fields total or more than 10 when you consider both documents? 100s of fields total across all documents is a tractable problem. thousands

Dynamic fields vs parent child

2017-06-26 Thread Saurabh Sethi
We have two requirements: 1. Indexing and storing event id and its timestamp. 2. Indexing and storing custom field name and value. The fields can be of any type, but for now lets say they are of types string, date and number. The events and custom fields for any solr document can easily be in hun