Use new json-event-parser create API

[pyropy]

This PR addresses breaking changed caused by automatic upgrade of json-event-parser create done by dependabot. New version of this package, although with minor semver upgrade, has a breaking API change.

[bajtos]

This PR addresses breaking changed caused by automatic upgrade of json-event-parser create done by dependabot. New version of this package, although with minor semver upgrade, has a breaking API change.

0.x versions don't provide any stability guarantees, see https://semver.org/#spec-item-4:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

[pyropy]

This PR addresses breaking changed caused by automatic upgrade of json-event-parser create done by dependabot. New version of this package, although with minor semver upgrade, has a breaking API change.

0.x versions don't provide any stability guarantees, see https://semver.org/#spec-item-4:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

I'm going to address this in our dependabot auto-merge workflow. It may cause issues in other repositories too as dependabot workflow was copied over from spark-evaluate repository.

[pyropy]

This PR addresses breaking changed caused by automatic upgrade of json-event-parser create done by dependabot. New version of this package, although with minor semver upgrade, has a breaking API change.

0.x versions don't provide any stability guarantees, see https://semver.org/#spec-item-4:
Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

I'm going to address this in our dependabot auto-merge workflow. It may cause issues in other repositories too as dependabot workflow was copied over from spark-evaluate repository.

I have addressed this problem in this PR #43

[bajtos]

It may cause issues in other repositories too as dependabot workflow was copied over from spark-evaluate repository.

It could cause issues, but we haven't experienced them yet.

We are auto-approving only selected dependencies. A trivial way to avoid this issue is excluding pre-1.0 dependencies from the list of dependencies to auto-approve.

Let's not worry about this in other repositories now; we have more important things to work on.

[bajtos]

Code changes LGTM.

I added 0331d69 to avoid event.clone().

Do you happen to have StateMarketDeals.json.zst around? It would be great to compare the output from the current and the new version, to ensure there are no regressions introduced.

[pyropy]

Code changes LGTM.

I added 0331d69 to avoid event.clone().

Do you happen to have StateMarketDeals.json.zst around? It would be great to compare the output from the current and the new version, to ensure there are no regressions introduced.

Sadly I don't have it but I'm going to download it for sake of testing.

[pyropy]

Code changes LGTM.
I added 0331d69 to avoid event.clone().
Do you happen to have StateMarketDeals.json.zst around? It would be great to compare the output from the current and the new version, to ensure there are no regressions introduced.

Sadly I don't have it but I'm going to download it for sake of testing.

@bajtos I've parsed StateMarketDeals.json.zst using two binaries, one using json-event-parser version 0.1.1. and the other one using the 0.2.0 version and compared files using cmp and they are equal.

[bajtos]

Sadly I don't have it but I'm going to download it for sake of testing.

@bajtos I've parsed StateMarketDeals.json.zst using two binaries, one using json-event-parser version 0.1.1. and the other one using the 0.2.0 version and compared files using cmp and they are equal.

Awesome, thanks for checking 🙏🏻