[
https://issues.apache.org/jira/browse/IGNITE-7691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443969#comment-16443969
]
Vladimir Ozerov commented on IGNITE-7691:
-----------------------------------------
Solution which makes sense to me:
1) Revert current patch
2) Return zero for precision and scale in JDBC
3) Return any sensible number in Spark, since we do not support scale/precision
anyway. It could be 0, -1, MAX_VALUE, whatever fit our needs
4) Disallow custom precision/scale in our new parser by default [1]
[1] https://issues.apache.org/jira/browse/IGNITE-6861
> Provide info about DECIMAL column scale and precision
> -----------------------------------------------------
>
> Key: IGNITE-7691
> URL: https://issues.apache.org/jira/browse/IGNITE-7691
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 2.4
> Reporter: Nikolay Izhikov
> Assignee: Nikolay Izhikov
> Priority: Minor
> Fix For: 2.6
>
>
> Currently, it impossible to obtain scale and precision of DECIMAL column from
> sql table metadata.
> Ignite should provide those type of meta information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
