[JBoss JIRA] (TEIID-2327) Add column masking
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2327?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2327:
-------------------------------------
+1
#2 seems more cohesive and is totally seems to be managed by configuration. #1 needs the hasRole that requires design time also makes hard to externalize with AuthorizationValidator interface for programmatic configuration.
> Add column masking
> ------------------
>
> Key: TEIID-2327
> URL: https://issues.jboss.org/browse/TEIID-2327
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> Support for column masking should be added to data roles. A typical approach would be to only affect the final projected values from user queries and have only one mask applicable at a time.
> A possibly related ability would be to hide columns (much like hidden tables) to our metadata.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (TEIID-2327) Add column masking
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2327?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2327:
---------------------------------------
There are two approaches to take:
1. use a new metadata representation:
<mask resource-name="">...</mask>
...
such that resource-name must be a fully qualified column name (although it would make more sense to use schema/object/column). This would be defined separately from data roles as there is only a single masking definition that is applicable to a given column. The expectation would be that the masking expression would be a case statement based upon hasRole.
or
2. add an ordered mask element to the permission metadata:
<mask order="1">...</mask>
Here we would determine the relevant mask by looking over all applicable roles for the mask with the lowest ordering.
I'm leaning toward the second representation as it makes masking well coupled with the role definition.
> Add column masking
> ------------------
>
> Key: TEIID-2327
> URL: https://issues.jboss.org/browse/TEIID-2327
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> Support for column masking should be added to data roles. A typical approach would be to only affect the final projected values from user queries and have only one mask applicable at a time.
> A possibly related ability would be to hide columns (much like hidden tables) to our metadata.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (TEIID-2486) Standalone CLI script has a small required change to work with EAP 6.1
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2486?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-2486:
------------------------------------
This is an EAP issue, they duplicated it. However, I've only tried this with EAP 6.1 ER5.
> Standalone CLI script has a small required change to work with EAP 6.1
> ----------------------------------------------------------------------
>
> Key: TEIID-2486
> URL: https://issues.jboss.org/browse/TEIID-2486
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.4
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 8.4
>
>
> The following command doesn't support the "name" attribute:
> /subsystem=threads/bounded-queue-thread-pool=teiid-async:add(name=teiid-async, max-threads=4, queue-length=100)
> This is the same issue seen in the domain script. So the command should be changed to be:
> /subsystem=threads/bounded-queue-thread-pool=teiid-async:add(max-threads=4, queue-length=100)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (TEIID-2486) Standalone CLI script has a small required change to work with EAP 6.1
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2486?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2486:
---------------------------------------
To clarify is this an EAP 6.1 issue (including alpha) or specific to a later 6.1 build?
> Standalone CLI script has a small required change to work with EAP 6.1
> ----------------------------------------------------------------------
>
> Key: TEIID-2486
> URL: https://issues.jboss.org/browse/TEIID-2486
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.4
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 8.4
>
>
> The following command doesn't support the "name" attribute:
> /subsystem=threads/bounded-queue-thread-pool=teiid-async:add(name=teiid-async, max-threads=4, queue-length=100)
> This is the same issue seen in the domain script. So the command should be changed to be:
> /subsystem=threads/bounded-queue-thread-pool=teiid-async:add(max-threads=4, queue-length=100)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (TEIID-2488) cache JBoss loggers
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2488:
-------------------------------------
Summary: cache JBoss loggers
Key: TEIID-2488
URL: https://issues.jboss.org/browse/TEIID-2488
Project: Teiid
Issue Type: Quality Risk
Components: Server
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.4
In some circumstances not caching loggers will create needless locking and logger creation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (TEIID-2487) Wrong aliasing when "supportsSelectExpression" is false in translator capabilities
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2487?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2487:
-------------------------------------
Thanks, I understand now. I was thinking "supportsSelectExpression" applies for aggregates too.
> Wrong aliasing when "supportsSelectExpression" is false in translator capabilities
> ----------------------------------------------------------------------------------
>
> Key: TEIID-2487
> URL: https://issues.jboss.org/browse/TEIID-2487
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> When "supportsSelectExpression" is false, in the translator capabilities and user submits a query like
> {code}
> select sum (intnum) as "sum" from smalla group by intkey order by "sum"
> {code}
> the pushdown command at the translator is
> {code}
> SELECT SUM(SMALLA.INTNUM) FROM SMALLA GROUP BY SMALLA.INTKEY ORDER BY c_0
> {code}
> The alias in the ORDER BY is wrong. Also do not understand why the query engine pushed the aggregate is being pushed, possibly due to "supportsAggregatesSum" is turned on.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (TEIID-2487) Wrong aliasing when "supportsSelectExpression" is false in translator capabilities
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2487?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2487.
-----------------------------------
Fix Version/s: 8.4
Resolution: Done
Updated the alias generator to account for non-column references when supportsSelectExpression is turned off.
> Wrong aliasing when "supportsSelectExpression" is false in translator capabilities
> ----------------------------------------------------------------------------------
>
> Key: TEIID-2487
> URL: https://issues.jboss.org/browse/TEIID-2487
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> When "supportsSelectExpression" is false, in the translator capabilities and user submits a query like
> {code}
> select sum (intnum) as "sum" from smalla group by intkey order by "sum"
> {code}
> the pushdown command at the translator is
> {code}
> SELECT SUM(SMALLA.INTNUM) FROM SMALLA GROUP BY SMALLA.INTKEY ORDER BY c_0
> {code}
> The alias in the ORDER BY is wrong. Also do not understand why the query engine pushed the aggregate is being pushed, possibly due to "supportsAggregatesSum" is turned on.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (TEIID-2487) Wrong aliasing when "supportsSelectExpression" is false in translator capabilities
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2487?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2487:
---------------------------------------
> Also do not understand why the query engine pushed the aggregate is being pushed, possibly due to "supportsAggregatesSum" is turned on
I don't follow you. supportsAggregateSum (and group by) has to be turned on or you wouldn't have it pushed down. The issue is alias generation is expecting all select clause expressions to be column references if supportsSelectExpression is turned off - this doesn't account for aggregates in the event that aggregate support is also enabled (for planning purposes grouping produces internal column references that are later prior to alias generation are substituted for their aggregate expression form).
> Wrong aliasing when "supportsSelectExpression" is false in translator capabilities
> ----------------------------------------------------------------------------------
>
> Key: TEIID-2487
> URL: https://issues.jboss.org/browse/TEIID-2487
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
>
> When "supportsSelectExpression" is false, in the translator capabilities and user submits a query like
> {code}
> select sum (intnum) as "sum" from smalla group by intkey order by "sum"
> {code}
> the pushdown command at the translator is
> {code}
> SELECT SUM(SMALLA.INTNUM) FROM SMALLA GROUP BY SMALLA.INTKEY ORDER BY c_0
> {code}
> The alias in the ORDER BY is wrong. Also do not understand why the query engine pushed the aggregate is being pushed, possibly due to "supportsAggregatesSum" is turned on.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (TEIID-2487) Wrong aliasing when "supportsSelectExpression" is false in translator capabilities
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2487:
-----------------------------------
Summary: Wrong aliasing when "supportsSelectExpression" is false in translator capabilities
Key: TEIID-2487
URL: https://issues.jboss.org/browse/TEIID-2487
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
When "supportsSelectExpression" is false, in the translator capabilities and user submits a query like
{code}
select sum (intnum) as "sum" from smalla group by intkey order by "sum"
{code}
the pushdown command at the translator is
{code}
SELECT SUM(SMALLA.INTNUM) FROM SMALLA GROUP BY SMALLA.INTKEY ORDER BY c_0
{code}
The alias in the ORDER BY is wrong. Also do not understand why the query engine pushed the aggregate is being pushed, possibly due to "supportsAggregatesSum" is turned on.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years