[teiid-issues] [JBoss JIRA] (TEIID-4532) Provide one-way or cryptographic hash functions

[Randall Hauch (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated TEIID-4532:
---------------------------------
    Description: 
Provide one-way or [cryptographic hash functions|https://en.wikipedia.org/wiki/SHA-3#Comparison_of_SHA_functions], such as any of the MD5, SHA-1, SHA-2, or SHA-3 functions, so that views can define columns that are hashes of other columns.

The goal is to allow views to hide some columns (e.g., personally identifying information), but to expose a new "primary key" that is a hash of other existing columns. So, given this source table:

{code:sql}
CREATE TABLE person (
  id INT PRIMARY KEY,
  name VARCHAR(256) NOT NULL,
  age INT,
  height INT,
  weight DOUBLE
);
{code}

a view could be created to hide the personally identifying information:

{code:sql}
CREATE VIEW anonymousPerson ()
  id VARCHAR(64) PRIMARY KEY,
  age INT,
  height INT,
  weight DOUBLE
) AS
   SELECT sha256(p.id, p.name) AS id, 
          p.age AS age, 
          p.height AS height, 
          p.weight AS weight 
          FROM person AS p;
{code}


  was:provide one-way or cryptographic hash functions, such as any of the MD5, SHA-1, SHA-2, or SHA-3 functions? https://en.wikipedia.org/wiki/SHA-3#Comparison_of_SHA_functions <https://en.wikipedia.org/wiki/SHA-3#Comparison_of_SHA_functions>



> Provide one-way or cryptographic hash functions
> -----------------------------------------------
>
>                 Key: TEIID-4532
>                 URL: https://issues.jboss.org/browse/TEIID-4532
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Common
>    Affects Versions: 9.2
>            Reporter: Van Halbert
>            Assignee: Steven Hawkins
>
> Provide one-way or [cryptographic hash functions|https://en.wikipedia.org/wiki/SHA-3#Comparison_of_SHA_functions], such as any of the MD5, SHA-1, SHA-2, or SHA-3 functions, so that views can define columns that are hashes of other columns.
> The goal is to allow views to hide some columns (e.g., personally identifying information), but to expose a new "primary key" that is a hash of other existing columns. So, given this source table:
> {code:sql}
> CREATE TABLE person (
>   id INT PRIMARY KEY,
>   name VARCHAR(256) NOT NULL,
>   age INT,
>   height INT,
>   weight DOUBLE
> );
> {code}
> a view could be created to hide the personally identifying information:
> {code:sql}
> CREATE VIEW anonymousPerson ()
>   id VARCHAR(64) PRIMARY KEY,
>   age INT,
>   height INT,
>   weight DOUBLE
> ) AS
>    SELECT sha256(p.id, p.name) AS id, 
>           p.age AS age, 
>           p.height AS height, 
>           p.weight AS weight 
>           FROM person AS p;
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)