[JBoss JIRA] (TEIID-3790) Restrict any authenticated roles
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3790?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3790:
----------------------------------
Fix Version/s: (was: 9.0)
(was: 8.12.x)
> Restrict any authenticated roles
> --------------------------------
>
> Key: TEIID-3790
> URL: https://issues.jboss.org/browse/TEIID-3790
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> A local connection with the pass-through flag set will allow any connection if no security domain is set (the 8.x default). Beyond that the role assignment logic will any authenticated roles to those users. We need to restrict any-authenticated roles to only properly authenticated users.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3582) Add the query requestID to all lines for that query in the logs
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3582?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3582.
-----------------------------------
Resolution: Done
Added teiid-request to the MDC, but not to the default log pattern. Also updated the docs.
> Add the query requestID to all lines for that query in the logs
> ---------------------------------------------------------------
>
> Key: TEIID-3582
> URL: https://issues.jboss.org/browse/TEIID-3582
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Van Halbert
> Fix For: 8.12.2
>
>
> Currently when running a query, the logs show the requestId on most of the lines but not all, especially CONNECTOR.
> for example, the following line doesn't have it:
> 14:13:34,071 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue13) Source-specific command: ....
> That's the problem. When lots of queries are running, user wants to grep through the log for that requestid and get just that one query's stuff.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3582) Add the query requestID to all lines for that query in the logs
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3582?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3582:
----------------------------------
Fix Version/s: 8.13
> Add the query requestID to all lines for that query in the logs
> ---------------------------------------------------------------
>
> Key: TEIID-3582
> URL: https://issues.jboss.org/browse/TEIID-3582
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Van Halbert
> Fix For: 8.13, 8.12.2
>
>
> Currently when running a query, the logs show the requestId on most of the lines but not all, especially CONNECTOR.
> for example, the following line doesn't have it:
> 14:13:34,071 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue13) Source-specific command: ....
> That's the problem. When lots of queries are running, user wants to grep through the log for that requestid and get just that one query's stuff.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3748) Impala translator - SELECT and HAVING statements are translating differently for Case statements
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3748?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3748:
----------------------------------
Issue Type: Quality Risk (was: Bug)
Fix Version/s: (was: 8.12.2)
Changing issue to a quality risk and pulling from 8.12.2 as it appears this is behavior introduced by the driver/impala. Will need more details to confirm.
> Impala translator - SELECT and HAVING statements are translating differently for Case statements
> ------------------------------------------------------------------------------------------------
>
> Key: TEIID-3748
> URL: https://issues.jboss.org/browse/TEIID-3748
> Project: Teiid
> Issue Type: Quality Risk
> Components: JDBC Connector
> Affects Versions: 8.11.4
> Environment: Ubuntu Trusty
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
> Labels: Impala_Translator, Translators
> Attachments: server.log
>
>
> Error from Impala-
> all DISTINCT aggregate functions need to have the same set of parameters as count(DISTINCT (CASE WHEN (secondcol >= 0) THEN 1 ELSE CAST(NULL AS STRING) END))
> deviating function: count(DISTINCT (CASE WHEN (secondcol >= 0) THEN 1 ELSE NULL END))
> Query:
> SELECT user_key, sum(firstcol),count(distinct case when secondcol >= 0 then 1 end)
> FROM sometable
> WHERE customer_key=6
> GROUP BY user_key
> HAVING sum(firstcol)>100
> AND count(distinct case when secondcol >= 0 then 1 end)=0
>
> Query explanation:
> For all users
> Add up values in the firstcol column (integer column)
> count distinct values in secondcol where secondcol value zero or more
> otherwise return null (output is string)
> Translated Teiid query:
> SELECT user_key, SUM(firstcol) as `EXPR_0`, COUNT(DISTINCT (CASE WHEN (secondcol >= 0) THEN '1' ELSE CAST(NULL AS STRING) END)) as `EXPR_1`
> FROM sometable
> WHERE customer_key` = 6
> HAVING (EXPR_0 > 100) AND (COUNT(DISTINCT (CASE WHEN (secondcol >= 0) THEN '1' ELSE NULL END)) = 0))
> Note the difference between the select and having for EXPR_1:
> Select - THEN '1' ELSE CAST(NULL AS STRING) END
> Having - THEN '1' ELSE NULL END
> Impala doesn't accept that these are the same aggregate function. Aliases aren't accepted in the HAVING.
> One further observation- if we swap the translation and write the statement in the select as
> COUNT(DISTINCT (CASE WHEN (secondcol >= 0) THEN '1' *ELSE NULL END*))
> Teiid translates the SELECT to
> COUNT(DISTINCT (CASE WHEN (secondcol >= 0) THEN '1' *ELSE CAST(NULL AS STRING) END*))
> So it always makes these mismatched.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3361) Add source query details to the command log
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3361?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3361.
-----------------------------------
Resolution: Partially Completed
Marking as partially completed for 8.12.1. Will add more sources in 8.12.x
> Add source query details to the command log
> -------------------------------------------
>
> Key: TEIID-3361
> URL: https://issues.jboss.org/browse/TEIID-3361
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.12.1
>
>
> The command log for convenience only contains the Teiid sql form of the source query. It would be good to have the translators also add their actual form of the source query when possible to the command log just to have a single place to track things down.
> Currently this info is logged to the CONNECTOR context inconsistently in each translator.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3800) Allow the parsing of a default expression
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3800:
-------------------------------------
Summary: Allow the parsing of a default expression
Key: TEIID-3800
URL: https://issues.jboss.org/browse/TEIID-3800
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.0
Now that we have an extension property, we could allow an expression to be used in parsing rather than just a string.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month
[JBoss JIRA] (TEIID-3799) Insert default expressions not rewritten
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3799:
-------------------------------------
Summary: Insert default expressions not rewritten
Key: TEIID-3799
URL: https://issues.jboss.org/browse/TEIID-3799
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.12
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.13, 8.12.2
Using the expression style default, the value may not be evaluated correctly because the rewritter is not run on the expression.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 1 month