Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make use of _allowMultipleMatches in FilteringParserDelegate #209

Closed
zazi opened this issue Aug 4, 2015 · 0 comments
Closed

Make use of _allowMultipleMatches in FilteringParserDelegate #209

zazi opened this issue Aug 4, 2015 · 0 comments

Comments

@zazi
Copy link

zazi commented Aug 4, 2015

Currently, it looks like that the _allowMultipleMatches attribute in FilteringGeneratorDelegate is not utilised (i.e. no value is assigned to this variable). Re. the documentation this attribute offers some useful functionality. So it would be nice, if it could be implemented properly. See https://groups.google.com/d/msg/jackson-user/VzZ94G9hvrs/JGFozl6lCQAJ
@cowtowncoder cowtowncoder changed the title make use of _allowMultipleMatches in FilteringGeneratorDelegate make use of _allowMultipleMatches in FilteringParserDelegate Dec 12, 2015
This was referenced Mar 20, 2016
Closed
Merged
@cowtowncoder cowtowncoder changed the title make use of _allowMultipleMatches in FilteringParserDelegate Make use of _allowMultipleMatches in FilteringParserDelegate Mar 22, 2016
dmikurube added a commit to embulk/embulk-util-json that referenced this issue Jul 3, 2023
@dmikurube
Allow multiple matches with JsonPointerBasedFilter
fc4971f 
JsonParser has not been working well with JSON Pointer for consequent multiple JSONs
when used with Jackson 2.7.4+.

For example of multiple JSONs in one stream: {"a": {"b": 1}} {"a": {"b": 2}}

It happened because Jackson 2.7.3 or earlier ignored the `allowMultipleMatches` option.
FasterXML/jackson-core#209

This commit fixes this problem by setting the option when used with Jackson 2.7.4+.
@dmikurube dmikurube mentioned this issue Jul 3, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zazi