Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-796

Avatica remote service truncates java.sql.Timestamp to milliseconds

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsAdd voteVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      TypedValue in Avatica read/writes java.sql.Timestamp in milliseconds even though natively the type supports nanosecond precision (and Phoenix does use the full precision). The JSON serialization protocol should count with this.

      I'd suggest serializing java.sql.Timestamp with `toString()` and deserializing with `valueOf()` if it's a string. Alternatively, it could be stored as a decimal number or just total number of nanoseconds.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned Assign to me
            lukaslalinsky Lukas Lalinsky

            Dates

              Created:
              Updated:

              Slack

                Issue deployment