[
https://issues.apache.org/jira/browse/ARROW-17729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Li updated ARROW-17729:
-----------------------------
Description:
Follow ups for ARROW-7744
* Rename internal classes to not imply everything is part of Flight RPC (e.g.
ArrowFlightJdbcArray -> FieldVectorArray or similar)
* Don't throw bare exceptions (always provide some error context)
* Log a warning if the {{arrow-flight:}} URI scheme is used instead of
{{arrow-flight-sql:}}
* Create a documentation page (that can be used for people approaching this
from the JDBC side, not necessarily Arrow users)
* Document the connection string format and parameters
* Replace {{// TODO}} comments with {{throw new
UnsupportedOperationException()}}
* Document how timestamp/time/date types are handled in converting between the
two type schemas
* Document the type conversions in general
* [timestamp handling is
suspect|https://github.com/apache/arrow/pull/13800#discussion_r938908230]
* Upgrade to JUnit5/AssertJ instead of JUnit4/Hamcrest
* Get rid of FreePortFinder
* Use a single (static?) RootAllocator with child allocators
* Remove all Guava usage (can we deny this with a lint?)
* See if {{SqlTypes}} can be folded into arrow-jdbc
was:
Follow ups for ARROW-7744
* Rename internal classes to not imply everything is part of Flight RPC (e.g.
ArrowFlightJdbcArray -> FieldVectorArray or similar)
* Don't throw bare exceptions (always provide some error context)
* Log a warning if the {{arrow-flight:}} URI scheme is used instead of
{{arrow-flight-sql:}}
* Create a documentation page (that can be used for people approaching this
from the JDBC side, not necessarily Arrow users)
* Document the connection string format and parameters
* Replace {{// TODO}} comments with {{throw new
UnsupportedOperationException()}}
* Document how timestamp/time/date types are handled in converting between the
two type schemas
* Document the type conversions in general
* [timestamp handling is
suspect|https://github.com/apache/arrow/pull/13800#discussion_r938908230]
* Upgrade to JUnit5/AssertJ instead of JUnit4/Hamcrest
* Get rid of FreePortFinder
* Use a single (static?) RootAllocator with child allocators
* Remove all Guava usage (can we deny this with a lint?)
> [Java][FlightRPC] Flight SQL JDBC driver improvements
> -----------------------------------------------------
>
> Key: ARROW-17729
> URL: https://issues.apache.org/jira/browse/ARROW-17729
> Project: Apache Arrow
> Issue Type: Improvement
> Components: FlightRPC, Java
> Reporter: David Li
> Priority: Major
>
> Follow ups for ARROW-7744
> * Rename internal classes to not imply everything is part of Flight RPC (e.g.
> ArrowFlightJdbcArray -> FieldVectorArray or similar)
> * Don't throw bare exceptions (always provide some error context)
> * Log a warning if the {{arrow-flight:}} URI scheme is used instead of
> {{arrow-flight-sql:}}
> * Create a documentation page (that can be used for people approaching this
> from the JDBC side, not necessarily Arrow users)
> * Document the connection string format and parameters
> * Replace {{// TODO}} comments with {{throw new
> UnsupportedOperationException()}}
> * Document how timestamp/time/date types are handled in converting between
> the two type schemas
> * Document the type conversions in general
> * [timestamp handling is
> suspect|https://github.com/apache/arrow/pull/13800#discussion_r938908230]
> * Upgrade to JUnit5/AssertJ instead of JUnit4/Hamcrest
> * Get rid of FreePortFinder
> * Use a single (static?) RootAllocator with child allocators
> * Remove all Guava usage (can we deny this with a lint?)
> * See if {{SqlTypes}} can be folded into arrow-jdbc
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
