GH-41287: [Java] ListViewVector Implementation

[vibhatha]

Rationale for this change

Apache Arrow format defines ListView and this has been introduced into other language bindings and the objective of this PR is to provide the initial ListView support to Java by adding ListViewVector.

Non-Goals

The following list of issues propose the extended work depending on this PR. They were separated to streamline the implementation process.

• [Java] LargeListViewVector Implementation #41272
• [Java] ListView Implementation for ColumnBinderArrowTypeVisitor in JDBC arrow-java#101
• [Java] LargeListView Implementation for ColumnBinderArrowTypeVisitor in JDBC arrow-java#98
• [Java] ListView implementation for AvaticaParameterBinder in JDBC arrow-java#100
• [Java] LargeListView implementation for AvaticaParameterBinder in JDBC arrow-java#99
• [Java] ListViewVector Implementation transferPair implementation #41269
• [Java] LargeListViewVector Implementation transferPair implementation #41291
• [Java] LargeListViewVector Implementation copy implementation #41292
• [Java] ListViewVector Implementation copy implementation #41270
• [Java] ListViewVector implementation for ConvertUtiils in JDBC arrow-java#97
• [Java] LargeListViewVector implementation for ConvertUtiils in JDBC arrow-java#96
• [Java] ListViewVector Implementation for UnionListViewReader #41569
• [Java] LargeListViewVector Implementation for UnionListViewReader #41570
• [Java] ListView Implementation for C Data Interface #41584
• [Java] LargeListView Implementation for C Data Interface #41585

Are these changes tested?

Yes

Are there any user-facing changes?

No

• GitHub Issue: [Java] ListViewVector Implementation #41287
• GitHub Issue: [Java] ListViewVector Implementation #41287

[github-actions]

Thanks for opening a pull request!

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

In the case of PARQUET issues on JIRA the title also supports:

PARQUET-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

See also:

• Other pull requests
• Contribution Guidelines - Contributing Overview

[vibhatha]

@lidavidm CIs are passing!

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit 0574988.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 5 possible false positives for unstable benchmarks that are known to sometimes produce them.