Skip to content

GH-47648: [Archery][Integration] More granularity in JSON test cases#47649

Merged
pitrou merged 1 commit intoapache:mainfrom
pitrou:gh47648-integration-granularity
Oct 1, 2025
Merged

GH-47648: [Archery][Integration] More granularity in JSON test cases#47649
pitrou merged 1 commit intoapache:mainfrom
pitrou:gh47648-integration-granularity

Conversation

@pitrou
Copy link
Member

@pitrou pitrou commented Sep 25, 2025

Rationale for this change

Separate binary columns from other primitives in the integration test cases, to make life easier when writing a new Arrow implementation.

Are these changes tested?

Yes, by integration CI test.

Are there any user-facing changes?

No, only for implementers who would use the generated files directly.

@github-actions github-actions bot added the awaiting review Awaiting review label Sep 25, 2025
@pitrou pitrou marked this pull request as ready for review September 25, 2025 08:07
@pitrou
Copy link
Member Author

pitrou commented Sep 25, 2025

@Alex-PLACET does this look ok?

@Alex-PLACET
Copy link

@pitrou perfect 👌

@pitrou
Copy link
Member Author

pitrou commented Sep 25, 2025

@alamb @tustvold @zeroshade Is it ok to you?

@pitrou
Copy link
Member Author

pitrou commented Sep 29, 2025

@paleolimbot

@github-actions github-actions bot added awaiting committer review Awaiting committer review and removed awaiting review Awaiting review labels Sep 30, 2025
Copy link
Member

@paleolimbot paleolimbot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good!

It was already not 1:1, but I found it confusing when I started out that the files in arrow-testing didn't quite align with the ones generated by Archery and I suppose this further widens that gap? The golden files in arrow-testing are easier to use than a full-on integration test for those getting started.

@github-actions github-actions bot added awaiting merge Awaiting merge and removed awaiting committer review Awaiting committer review labels Sep 30, 2025
@pitrou
Copy link
Member Author

pitrou commented Sep 30, 2025

It was already not 1:1, but I found it confusing when I started out that the files in arrow-testing didn't quite align with the ones generated by Archery and I suppose this further widens that gap?

For the old files, yes, but the plan is to add a set of more recent "golden" files generated with Arrow 21: #47635

@pitrou pitrou force-pushed the gh47648-integration-granularity branch from 16922e5 to 1b7808c Compare September 30, 2025 18:52
@pitrou
Copy link
Member Author

pitrou commented Sep 30, 2025

@zeroshade How can we make these errors go away on the integration tests? They've been happening randomly for quite some time.


  + go install -v ./...
  type_traits_boolean.go:20:2: cannot find package "github.com/apache/arrow-go/v18/arrow/bitutil" in any of:
  	/opt/go/src/github.com/apache/arrow-go/v18/arrow/bitutil (from $GOROOT)
  	/go/src/github.com/apache/arrow-go/v18/arrow/bitutil (from $GOPATH)
  datatype_fixedwidth.go:25:2: cannot find package "github.com/apache/arrow-go/v18/arrow/decimal" in any of:
  	/opt/go/src/github.com/apache/arrow-go/v18/arrow/decimal (from $GOROOT)
  	/go/src/github.com/apache/arrow-go/v18/arrow/decimal (from $GOPATH)
  datatype_viewheader.go:23:2: cannot find package "github.com/apache/arrow-go/v18/arrow/endian" in any of:
  	/opt/go/src/github.com/apache/arrow-go/v18/arrow/endian (from $GOROOT)
  	/go/src/github.com/apache/arrow-go/v18/arrow/endian (from $GOPATH)
  type_traits.go:24:2: cannot find package "github.com/apache/arrow-go/v18/arrow/float16" in any of:
  	/opt/go/src/github.com/apache/arrow-go/v18/arrow/float16 (from $GOROOT)
  	/go/src/github.com/apache/arrow-go/v18/arrow/float16 (from $GOPATH)
  datatype.go:24:2: cannot find package "github.com/apache/arrow-go/v18/arrow/internal/debug" in any of:
  	/opt/go/src/github.com/apache/arrow-go/v18/arrow/internal/debug (from $GOROOT)
  	/go/src/github.com/apache/arrow-go/v18/arrow/internal/debug (from $GOPATH)

[etc.]

@pitrou
Copy link
Member Author

pitrou commented Sep 30, 2025

Ok, it should be fixed by #47674

…cases

Separate binary columns from other primitives in the integration test cases, to make life easier when writing a new Arrow implementation.
@pitrou pitrou force-pushed the gh47648-integration-granularity branch from 1b7808c to c755612 Compare October 1, 2025 06:19
@pitrou pitrou merged commit eb9d519 into apache:main Oct 1, 2025
7 checks passed
@pitrou pitrou removed the awaiting merge Awaiting merge label Oct 1, 2025
@pitrou pitrou deleted the gh47648-integration-granularity branch October 1, 2025 06:47
@conbench-apache-arrow
Copy link

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

There were no benchmark performance regressions. 🎉

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

zanmato1984 pushed a commit to zanmato1984/arrow that referenced this pull request Oct 15, 2025
…cases (apache#47649)

### Rationale for this change

Separate binary columns from other primitives in the integration test cases, to make life easier when writing a new Arrow implementation.

### Are these changes tested?

Yes, by integration CI test.

### Are there any user-facing changes?

No, only for implementers who would use the generated files directly.

* GitHub Issue: apache#47648

Authored-by: Antoine Pitrou <antoine@python.org>
Signed-off-by: Antoine Pitrou <antoine@python.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants