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

Json codec builds nested fields when field name contains square brackets

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

Nobody has claimed this yet.

Assessment

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

Research direction

Reproduce the issue with the JSON example in the report and trace the codec's handling of field names containing square brackets. Confirm how the input is converted into nested fields, then ensure the literal field name is preserved and verify the same example no longer produces nested keys.

Written by the indexing model from the issue text.

Description

1.5.0-rc3

Hi,

Facing problem (upgrading from 1.4.2 to 2.0 that occurs when field have brackets inside (valid JSON)

example:
{
"dynamo_entry_tuple_in_list[0]_list[0]": "valid-value"
}

is converted to:

{
"dynamo_entry_tuple_in_list" : {"0_.list":{"1_":null,"0_":null}}
}

because my fields contains dots (removed in "de_dot") I'm unable to rename them in filter - it becomes nested.

Dominant language
Ruby
Stars
26
Forks
27
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-codec-json

All issues in logstash-plugins/logstash-codec-json

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.