You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Francis Chuang (Jira)" <ji...@apache.org> on 2024/03/25 07:49:00 UTC

[jira] [Resolved] (CALCITE-6339) Replace hashicorp/go-uuid with google/uuid

     [ https://issues.apache.org/jira/browse/CALCITE-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francis Chuang resolved CALCITE-6339.
-------------------------------------
    Resolution: Fixed

> Replace hashicorp/go-uuid with google/uuid
> ------------------------------------------
>
>                 Key: CALCITE-6339
>                 URL: https://issues.apache.org/jira/browse/CALCITE-6339
>             Project: Calcite
>          Issue Type: Task
>          Components: avatica-go
>            Reporter: Francis Chuang
>            Assignee: Francis Chuang
>            Priority: Minor
>             Fix For: avatica-go-5.4.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The hashicorp/uuid library generates strings that look like uuids but are purely random. It is also not as popular or as active as the google/uuid library.
> The google/uuid library generates real uuids that are RFC compliant. The library is also more popular and actively maintained.
> These ids are used to generate connection ids, so whether they are RFC compliant or not is inconsequential, however, it is a good idea to generate compliant uuids if downstream users behind avatica expects correct and compliant uuids.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)