[
https://issues.apache.org/jira/browse/FLINK-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551739#comment-16551739
]
ASF GitHub Bot commented on FLINK-7205:
---------------------------------------
GitHub user buptljy opened a pull request:
https://github.com/apache/flink/pull/6381
[FLINK-7205] [table&sql]Add UUID supported in SQL and TableApi
## What is the purpose of the change
* Add UUID supported in SQL and TableApi.
## Brief change log
* Add UUID function.
## Verifying this change
* Unit tests.
## Documentation
* add in table.md and sql.md
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/buptljy/flink FLINK-7205
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/6381.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #6381
----
commit 5cde30f8feb2feb49dc1381af3d1d288c39122f0
Author: wind <bupt_ljy@...>
Date: 2018-07-21T15:20:21Z
add uuid table&sql function
commit 8829de68bee64c6709d55efd17c09beabdb7a8be
Author: wind <bupt_ljy@...>
Date: 2018-07-21T15:32:42Z
add docs for uuid
----
> 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 & 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)
