Dmitri Bourlatchkov

@asheeshgarg : how flexible is your env.? Can you afford repackaging Nessie jars?

@asheeshgarg : For a workaround please try this: 1. Do not add any extra jars to the Spark's `jars` directory 2. Use the `--jars` option instead to add the pre-downloaded...

@ajantha-bhat : Could the "entity too large" exception be coming the JSON parser?

Site note: Nessie should probably surface the 413 error in this case, but it looks like the client is getting 400 instead.

It might be convenient to address #2392 as well, when we change how CLI gets user input for building a new commit.

For background: the default `127.255.0.0` address was initially added to avoid startup failure because OIDC address had to be configured. Might be worth checking if it can be left blank...

Good point! I was thinking about server properties in the `/config` end point, but adding a dedicated endpoint to return a `RepositoryDescription` is even better.

I do not think this issue is particular to Nessie API v2 in the sense of REST paths and parameters. We're not changing how tokens are passed to the server....

rebased

I've squashed some of the review-based changes into the main (first) commit because the affected code got many changes from related PRs and the interplay of changes was becoming awkward....