Jordan Sissel

```diff diff --git a/spec/codecs/json_spec.rb b/spec/codecs/json_spec.rb index f86f2b9..a774f7f 100644 --- a/spec/codecs/json_spec.rb +++ b/spec/codecs/json_spec.rb @@ -188,4 +188,15 @@ describe LogStash::Codecs::JSON do end end + context "when given invalid json" do + context...

I am open to input on a better setting name than `escaped_hex_codes`

I don't' think there's any practical standard for what constitutes "CSV" but my rough understanding was that fields were comma-delimited and sometimes quotes were used for values. Spaces outside of...

I tested loading csv into LibreCalc with a few variants of `"one","two","three"` with spaces in various places, and things seem like they are loaded successfully.

After research above, I am agreeing this is a bug. We use the Ruby standard library CSV parser for this filter, and I don't see any mechanism in the CSV...

I will work on this soon. I think we can come up with a workable solution; will report back soon.

@burdandrei haha, thank you for the offer of help! I'm hoping we can make a patch of some kind available soon that we'd love help testing. Stay tuned. :)

+1

As a workaround, you can use single quotes: ``` query => 'type:start AND operation:"%{[opid]}"' ```

Howdy! Sorry for the delays. I like the idea as proposed. I have a question about the behavior, though. It feels like the escaped characters should be interpreted before storing...