Indexing text from nested objects
See original GitHub issueCreated from this initial discussion.
Description
Allow for nested objects to provide content for a field. Similar to indexing an array of strings from an object, but an additional delegate needs to be provided to read the text from each of the nested objects in turn.
.WithField(
"Captions", // The name of the field to record all the nested object text under
v => v.CaptionTracks, // The set of nested objects
ct => ct.GetFullText()) // A delegate to read the text for each nested object
Issue Analytics
- State:
- Created 8 months ago
- Reactions:1
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Setting a nested value of an object using a string ...
1 Answer. Explanation : The test string holds the location of the arrayOfStrings and holds both indices for array, and keys for objects....
Read more >How to create Search Index for text field inside nested ...
So I have a nested array of objects. I do a $Search full text search on a nested object in a nested array...
Read more >Indexing Nested Child Documents
Solr supports indexing nested documents, described here, and ways to search and retrieve them very efficiently. By way of example, nested documents in...
Read more >Nested field type | Elasticsearch Guide [8.9]
The nested type is a specialised version of the object data type that allows arrays of objects to be indexed in a way...
Read more >Nested Property Index - Docs
An index can be defined on a nested property to improve performance of nested queries - this is highly recommended. Nested properties indexing...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Merging this with #69
@h0lg yeah, that makes sense. The serialized file format doesn’t contain any of the extra information needed about the dynamic fields, so when it’s deserialized the index data structures will contain references to field numbers that no longer exist. 😒
I’ll have a look at what’s needed to extend the format to include and rehydrate it into a new index.