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

Cannot use \n as a terminator that isn't the default

Open
#4 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the split filter configuration with an explicit "\n" terminator, then compare it with the default behavior and the requested "\n\n" case. Trace how the terminator value is handled and add a regression test showing that explicit newline strings split as expected.

Written by the indexing model from the issue text.

Description

Using the split filter and not specifying a terminator (by default uses \n) works fine, as in it splits on newlines. However, if I do specify the terminator as follows:

split {
  terminator => "\n"
}

Then it does not work, as in it does not split on newlines. I took a peek at the source code and it did not seem that this should be a problem as it is just a string representation though...

The use case I had found this in was when trying to actually split on \n\n instead.

Dominant language
Ruby
Stars
6
Forks
29
PR merge metrics
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.