Use extractField to extract document id field
See original GitHub issueI’ve found that using a document structure with an id that is nested, like this for example where tracker.id
is the document id:
{
tracker : {
id : 'documentId',
...
},
asset : { ... }
}
is not possible. I’m not sure if there are other considerations preventing this, but it seems as if using extractField to extract the idField in addition to regular fields might solve the issue. I would like to avoid changing the document structure if possible.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
ExtractField | Confluent Documentation
This document provides usage information for the Apache Kafka SMT ... snippet below shows how to use ExtractField to extract the field name...
Read more >Extract fields with search commands - Splunk Documentation
Extract fields with search commands. You can use search commands to extract fields in different ways. The rex command performs field ...
Read more >kafka connect transformations, ValueToKey & ExtractField
Let's say you're using Kafka Connect Elasticsearch. With default settings, document id in elasticsearch would be in following format.
Read more >Field extraction | Elasticsearch Guide [8.5] | Elastic
Dissect extracts structured fields out of text, using delimiters to define the matching pattern. Unlike grok, dissect doesn't use regular expressions. Let's ...
Read more >SnpSift Extract Fields - SnpEff & SnpSift Documentation
Example 2: Extracting genotype fields. $ java -jar SnpSift.jar extractFields file.vcf "CHROM" "POS" "ID" "THETA" "GEN[0].GL[1]" "GEN[1].GL" "GEN[3].
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
Hi @mquinn-leverege , this issue is resolved by this commit, now the ID field is consistent with the other fields, and its extraction can be customized with
extractField
.This change is already released as part of version
v2.5.0
. This should solve your case, so I will close this issue, but feel free to comment if not.PS: It could be nice to create a expo gallery in the documentation or github wiki to link projects using minisearch so people could look at real-life/production examples.