docs: update onboarding steps for Java v3 client

[karel-rehor]

Updates the onboarding steps for the Java v3 client.
Introduces new library features.

• Query parameters
• Up to date Write API

Checklist

Authors and Reviewer(s), please verify the following:

• A PR description, regardless of the triviality of this change, that communicates the value of this PR
• Well-formatted conventional commit messages that provide context into the change
• Documentation updated or issue created (provide link to issue/PR)
• Signed CLA (if not already signed)
• Feature flagged, if applicable

[wdoconnell]

Hi @karel-rehor - thank you, I had a few observations here:

1. This variant of the onboarding flow is behind the ioxOnboarding feature flag, so it won't be shown for any users with that flag disabled; the Flux onboarding will otherwise be shown. That flag is enabled generally, but I will check with others if that is the right approach here.
2. This makes the Java onboarding examples a good amount longer - I am not sure if that is desirable unless this is also intended as a bug fix or for some other purpose. Can you speak to the motivation behind the work?
3. Not absolutely necessary in all cases, but for a PR like this that has visual impact on the flow, I usually find it is helpful for the review to include a video illustrating what was changed.

[wdoconnell]

Are we updating this query due to a failure with the test dataset, or is this simply designed to illustrate a different principle?

[karel-rehor]

Query parameters are a feature added in the 0.6.0 client library release from March of last year.

The text above the snippet briefly introduces them: "The following code replaces the fixed values of "bees" and "ants" with the parameters $species1 and $species2."

We thought users would like to be made aware of this feature. A number of users requested it and are now using it.

[wdoconnell]

I might correct "means" to "This requires setting the following JVM argument"

[karel-rehor]

updated

[wdoconnell]

I don't think we should qualify whether the script is 'straightforward' since it should speak for itself -- "This can be done with an environment variable" should be enough.

[karel-rehor]

updated

[wdoconnell]

Remocal failure in CI looks transient, so I am re-running the tests.

[karel-rehor]

Hi @wdoconnell

1. This variant of the onboarding flow is behind the ioxOnboarding feature flag, so it won't be shown for any users with that flag disabled; the Flux onboarding will otherwise be shown. That flag is enabled generally, but I will check with others if that is the right approach here.

My understanding is that we primarily want these changes visible to cloud users and in the cloud interface, which, if I understand correctly, should have ioxOnboarding enabled.

2. This makes the Java onboarding examples a good amount longer - I am not sure if that is desirable unless this is also intended as a bug fix or for some other purpose. Can you speak to the motivation behind the work?

The influxdb3 client libraries have evolved considerably since these onboarding steps were first written. Since the beginning of December client libraries are progressively being released to the first major version 1.0 (and in the case of go 2.0) because of breaking changes. The new onboarding steps illustrate the following features added in the past last year:

• Query parameters
• Arrow flight support for queries
• Handling of null/nil values
• Leveraging Arrow metadata during deserialization

I also though it would be helpful to organize test data into a POJO as it is a common Java idiom,

3. Not absolutely necessary in all cases, but for a PR like this that has visual impact on the flow, I usually find it is helpful for the review to include a video illustrating what was changed.

OK, I thought that I would need to take time to compress the screencast file, as in the past I had encountered a 10MB limit, but it seems this can be added. This shows only the workflow without pasting snippets to an IDE.

Screencast.from.08-01-25.10.57.08.webm