Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Allow target to the root of the document

Open
  • Is something wrong?
#16 1 comment 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
data

Research direction

The issue names the Ruby plugin and its target parameter but no file or test. Start by locating target handling and the existing split-filter tests; done means supporting a root-level target that produces events containing each array element's fields without the MyArray wrapper.

Written by the indexing model from the issue text.

Description

enhancement

Input like this:

{ "MyArray": [ { "id": 1}, { "id": 2} ] }

will correctly make two events, but the data from the array will be location under a field named "MyArray", e.g.:

{
    "MyArray": {
        "id": 1
    }
},
{
    "MyArray": {
        "id": 2
    }
}

While you can specify a 'target' param to put the field somewhere else, there's no info on how to put the new fields at the root level of the new events, e.g.

{
    "id": 1
},
{
    "id": 2
}

This would prevent people from having to drop into ruby to move an arbitrary list of fields.

Dominant language
Ruby
Stars
6
Forks
29
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from logstash-plugins/logstash-filter-split

All issues in logstash-plugins/logstash-filter-split

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.