I would like to store JSON data in a column and have it analyzed by the DSE search as a document and not as a text field.
I cannot coerce the JSON docs into a table because they do not follow a common schema (or any reasonably sized set of schema)
What I have currently is a working wildcard search over a large text field which performs poorly and does not allow for more sophisticated queries.
I have read that SOLR supports nested documents but the documentation is not enough to be applied to DSE. There seems to be no SOLR field type for nested docs and I have no idea how to apply restrictions to object names like _childDocuments_ as seen here
Is it possible to have DSE search handle fields/columns as separate or nested documents and if yes, how do I configure and use it?
Thank you
Seems to me that if you can't use UDTs the other option is field transformers. (link below)
To answer the comment question. Indexing a JSON document stored in a record as a nested/separate document is totally possible. The main issue here is that the data doesn't seem to have any rime or reason to the format. This makes it extremely hard to handle as to make a schema you would normally use the structure of the JSON. If my understanding is correct there isn't really as structure to work with here.