Support cooking data
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 15
Description
The TA runner can read props.conf and transforms.conf.
By default, it will only use the SHOULD_LINEMERGE setting to send data as a combined entry or a set of entries, one per line.
The TA runner could potentially apply most of the indexing time transformations, thereby reducing the work of the indexer which can then ingest the data directly.
- Find if field aliases are index or search time
- support indexed extractions
- support ingest eval
- support rulesets
- support transforms
- support multiline merges
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining how the TA runner currently reads props.conf and transforms.conf, and how SHOULD_LINEMERGE produces combined or line-based entries. The unchecked items define the proposed scope: field aliases, indexed extractions, ingest eval, rulesets, and multiline merges; done would require deciding which indexing-time transformations are supported and implementing them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100