You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/04/25 02:03:40 UTC

[GitHub] [dolphinscheduler] paul8263 commented on issue #9661: [Improvement][Backend] Long precision might lost

paul8263 commented on issue #9661:
URL: https://github.com/apache/dolphinscheduler/issues/9661#issuecomment-1107987563

   Hi @Tianqi-Dotes ,
   JavaScript `Number.MAX_SAFE_INTEGER` returns 2 to the power of 53 - 1, which is able to store int(x) in MySQL.
   
   However not all `id` columns of the tables in DS are defined as int(x). Some of them are typed bigint(x). I don't know why we need this.
   
   I think if there is not need to calculate or compare long value in the front end, it would be safe to convert them to strings, as configuring a global serializer for long type in Jackson.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org