Skip to content

Do we need to publish arrow-integration-test to crates.io? #10470

Description

@Jefffrey

It seems odd that in our list of crates to publish, we see that crate:

```shell
(cd arrow-buffer && cargo publish)
(cd arrow-schema && cargo publish)
(cd arrow-data && cargo publish)
(cd arrow-array && cargo publish)
(cd arrow-select && cargo publish)
(cd arrow-ord && cargo publish)
(cd arrow-cast && cargo publish)
(cd arrow-ipc && cargo publish)
(cd arrow-csv && cargo publish)
(cd arrow-json && cargo publish)
(cd arrow-avro && cargo publish)
(cd arrow-arith && cargo publish)
(cd arrow-string && cargo publish)
(cd arrow-row && cargo publish)
(cd arrow-pyarrow && cargo publish)
(cd arrow && cargo publish)
(cd arrow-avro && cargo publish)
(cd arrow-flight && cargo publish)
(cd parquet-variant && cargo publish)
(cd parquet-variant-json && cargo publish)
(cd parquet-variant-compute && cargo publish)
(cd parquet-geospatial && cargo publish)
(cd parquet && cargo publish)
(cd parquet_derive && cargo publish)
(cd arrow-integration-test && cargo publish)
```

https://crates.io/crates/arrow-integration-test/59.1.0 🤔

Indeed we have documentation & discussion that its meant only for internal use:

It seems its only usage is in arrow-integration-testing, but this is already via a local dependency and this crate is not published either

arrow-integration-test = { path = "../arrow-integration-test", default-features = false }

Can we stop publishing this crate if it is not meant to be external?

Metadata

Metadata

Assignees

No one assigned

    Labels

    development-processRelated to development process of arrow-rsquestionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions