flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7205) Add UUID supported in TableAPI/SQL
Date Mon, 13 Aug 2018 12:23:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578199#comment-16578199
] 

ASF GitHub Bot commented on FLINK-7205:
---------------------------------------

twalthr commented on a change in pull request #6381: [FLINK-7205] [table] Add UUID supported
in SQL and TableApi
URL: https://github.com/apache/flink/pull/6381#discussion_r209585954
 
 

 ##########
 File path: flink-libraries/flink-table/src/test/scala/org/apache/flink/table/expressions/ScalarFunctionsTest.scala
 ##########
 @@ -500,6 +500,39 @@ class ScalarFunctionsTest extends ScalarTypesTestBase {
       "null")
   }
 
+  @Test
+  def testUUID(): Unit = {
+    testAllApis(
+      CharLength(uuid()),
 
 Review comment:
   Use the implicit methods here and in the following lines instead? `.charLength()`, `.substring()`?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Add UUID supported in TableAPI/SQL
> ----------------------------------
>
>                 Key: FLINK-7205
>                 URL: https://issues.apache.org/jira/browse/FLINK-7205
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table API &amp; SQL
>    Affects Versions: 1.4.0
>            Reporter: sunjincheng
>            Assignee: buptljy
>            Priority: Major
>              Labels: pull-request-available
>
> UUID() returns a value that conforms to UUID version 1 as described in RFC 4122. The
value is a 128-bit number represented as a utf8 string of five hexadecimal numbers in aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee
format:
> The first three numbers are generated from the low, middle, and high parts of a timestamp.
The high part also includes the UUID version number.
> The fourth number preserves temporal uniqueness in case the timestamp value loses monotonicity
(for example, due to daylight saving time).
> The fifth number is an IEEE 802 node number that provides spatial uniqueness. A random
number is substituted if the latter is not available (for example, because the host device
has no Ethernet card, or it is unknown how to find the hardware address of an interface on
the host operating system). In this case, spatial uniqueness cannot be guaranteed. Nevertheless,
a collision should have very low probability.
> See: [RFC 4122: http://www.ietf.org/rfc/rfc4122.txt|http://www.ietf.org/rfc/rfc4122.txt]
> See detailed semantics:
>    MySql: [https://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html#function_uuid|https://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html#function_uuid]
> Welcome anybody feedback -:).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message