feat(ruby): don't use adbc-arrow-glib #3221
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
adbc-arrow-glib depends on arrow-glib.
In general, arrow-glib is released as major version release frequently. Our adbc-arrow-glib deb/rpm packages may refer old arrow-glib binaries soon. If the adbc-arrow-glib deb/rpm packages refer old arrow-glib binaries, both of old arrow-glib and new arrow-glib (via red-arrow gem) may be used in the same process. It causes some problems such as "File already exists in database: orc_proto.proto".
We can implement red-arrow integration without adbc-arrow-glib by C data interface. So, let's avoid using adbc-arrow-glib.
Fixes #3178.