Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] JDBC Driver reports DATE max size incorrectly #21

Closed
kylepbit opened this issue Oct 17, 2022 · 1 comment · Fixed by #39
Closed

[BUG] JDBC Driver reports DATE max size incorrectly #21

kylepbit opened this issue Oct 17, 2022 · 1 comment · Fixed by #39
Labels
bug Something isn't working

Comments

@kylepbit
Copy link

What is the bug?
The getDataTypes() call returns a row for the DATE type, and returns the max size as 24 instead of the correct 10. 24 is used for timestamp, not date.

How can one reproduce the bug?
Steps to reproduce the behavior:

  1. Connect to OpenSearch using the JDBC driver using any custom app or tool like DbVisualizer
  2. Open or invoke the data types
  3. Locate the DATE entry
  4. See the MAX_SIZE column reported as 24 instead of 10

What is the expected behavior?
The MAX_SIZE should be 10 instead of 24.

What is your host/environment?

  • OS: macOS Monterey
  • Version JDBC driver v 1.1.0.1
  • Plugins
@kylepbit kylepbit added the bug Something isn't working label Oct 17, 2022
@acarbonetto
Copy link
Collaborator

Related to opensearch-project/sql#794

@Yury-Fridlyand Yury-Fridlyand mentioned this issue Dec 8, 2022
Merged
6 tasks
@MitchellGale MitchellGale mentioned this issue Dec 10, 2022
Open
@dai-chen dai-chen transferred this issue from opensearch-project/sql Dec 14, 2022
@Yury-Fridlyand Yury-Fridlyand mentioned this issue Dec 19, 2022
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix default precision and maxSize for all datetime types. Bit-Quill/sql-jdbc
2 participants
@kylepbit @acarbonetto