[JBoss JIRA] (TEIID-2800) Teiid Login Issue with special characters
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2800?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2800:
---------------------------------------
>So after this change, we should set the user/password parameters directly on teiidDataSource
Before this change if you set a property on TeiidDataSource that needs url encoding, it will need to be encoded form. After this change properties such as user/password on the TeiidDataSource will not need to be encoded.
> If the user password is passed to getConnection() it will not be encoded. Am I correct?
Before this change user/password on getConnection(user, password) are ignored. After this change, they will be used and do not need to be encoded.
> Teiid Login Issue with special characters
> -----------------------------------------
>
> Key: TEIID-2800
> URL: https://issues.jboss.org/browse/TEIID-2800
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.1
> Environment: Mainframe Jboss 7.1.1
> Reporter: Gautam Banerjee
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.7
>
>
> When we try to login to teiid programmatically through datasource, we are having problem with username having special characters.
> We are encoding the special character as per url encoding
> eg : username %xyz is encoded as %25xyz but teiid does not decode the special character while passing username. So the username passed by teiid is %25xyz which fails authentication as the actual username is %xyz
--
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
10 years, 12 months
[JBoss JIRA] (TEIID-2800) Teiid Login Issue with special characters
by Gautam Banerjee (JIRA)
[ https://issues.jboss.org/browse/TEIID-2800?page=com.atlassian.jira.plugin... ]
Gautam Banerjee edited comment on TEIID-2800 at 1/16/14 1:52 AM:
-----------------------------------------------------------------
So after this change, we should set the user/password parameters directly on teiidDataSource. If the user password is passed to getConnection() it will not be encoded. Am I correct?
was (Author: gtmbanerjee):
So after this change, we should set the user/password parameters directly on teiidDataSource. If the user password is not passed to getConnection() it will not be encoded. Am I correct?
> Teiid Login Issue with special characters
> -----------------------------------------
>
> Key: TEIID-2800
> URL: https://issues.jboss.org/browse/TEIID-2800
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.1
> Environment: Mainframe Jboss 7.1.1
> Reporter: Gautam Banerjee
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.7
>
>
> When we try to login to teiid programmatically through datasource, we are having problem with username having special characters.
> We are encoding the special character as per url encoding
> eg : username %xyz is encoded as %25xyz but teiid does not decode the special character while passing username. So the username passed by teiid is %25xyz which fails authentication as the actual username is %xyz
--
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
10 years, 12 months
[JBoss JIRA] (TEIID-2800) Teiid Login Issue with special characters
by Gautam Banerjee (JIRA)
[ https://issues.jboss.org/browse/TEIID-2800?page=com.atlassian.jira.plugin... ]
Gautam Banerjee commented on TEIID-2800:
----------------------------------------
So after this change, we should set the user/password parameters directly on teiidDataSource. If the user password is not passed to getConnection() it will not be encoded. Am I correct?
> Teiid Login Issue with special characters
> -----------------------------------------
>
> Key: TEIID-2800
> URL: https://issues.jboss.org/browse/TEIID-2800
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.1
> Environment: Mainframe Jboss 7.1.1
> Reporter: Gautam Banerjee
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.7
>
>
> When we try to login to teiid programmatically through datasource, we are having problem with username having special characters.
> We are encoding the special character as per url encoding
> eg : username %xyz is encoded as %25xyz but teiid does not decode the special character while passing username. So the username passed by teiid is %25xyz which fails authentication as the actual username is %xyz
--
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
10 years, 12 months
[JBoss JIRA] (TEIID-2802) HIVE2: got Invalid table alias or column reference when running UNION ALL query on HIVE2
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2802?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2802:
---------------------------------------
So more than likely this would happen even without the union as it seems like the presence of the grouping requires the order by to use the output names from the select clause. Can you confirm if the direct to Hive (not through Teiid) query:
SELECT v_0.c_0 FROM (SELECT c_0 FROM (SELECT g_1.name AS c_0 FROM
opportunities_small g_1 UNION ALL SELECT g_0.name AS c_0 FROM opportunities
g_0) X__) v_0 GROUP BY v_0.c_0 ORDER BY c_0
works as expected.
> HIVE2: got Invalid table alias or column reference when running UNION ALL query on HIVE2
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-2802
> URL: https://issues.jboss.org/browse/TEIID-2802
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: TEIID with HIVE2
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
>
> If I tried to combine 2 tables from a same HIVE2 data source using UNION ALL, I got "Invalid table alias or column reference" error.
> Query that I submitted to Teiid originally:
> select "name"
> from (Select * from hive2.opportunities_small UNION ALL Select * from
> hive2.opportunities) "query"
> group by "name"
> order by "name"
> Query that Teiid generated:
> SELECT v_0.c_0 FROM (SELECT c_0 FROM (SELECT g_1.name AS c_0 FROM
> opportunities_small g_1 UNION ALL SELECT g_0.name AS c_0 FROM opportunities
> g_0) X__) v_0 GROUP BY v_0.c_0 ORDER BY v_0.c_0
> Error:
> Invalid table alias or column reference 'v_0': (possible column names are: c_0)
--
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
10 years, 12 months
[JBoss JIRA] (TEIID-2802) HIVE2: got Invalid table alias or column reference when running UNION ALL query on HIVE2
by Ivan Chan (JIRA)
[ https://issues.jboss.org/browse/TEIID-2802?page=com.atlassian.jira.plugin... ]
Ivan Chan commented on TEIID-2802:
----------------------------------
It works with only order by or group by, but not order by and group by together.
It is ok to run the following queries:
select "name"
from (Select * from hive2.opportunities_small UNION ALL Select * from
hive2.opportunities) "query"
group by "name"
select "name"
from (Select * from hive2.opportunities_small UNION ALL Select * from
hive2.opportunities) "query"
order by "name"
but not this one:
select "name"
from (Select * from hive2.opportunities_small UNION ALL Select * from
hive2.opportunities) "query"
group by "name"
order by "name"
> HIVE2: got Invalid table alias or column reference when running UNION ALL query on HIVE2
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-2802
> URL: https://issues.jboss.org/browse/TEIID-2802
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: TEIID with HIVE2
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
>
> If I tried to combine 2 tables from a same HIVE2 data source using UNION ALL, I got "Invalid table alias or column reference" error.
> Query that I submitted to Teiid originally:
> select "name"
> from (Select * from hive2.opportunities_small UNION ALL Select * from
> hive2.opportunities) "query"
> group by "name"
> order by "name"
> Query that Teiid generated:
> SELECT v_0.c_0 FROM (SELECT c_0 FROM (SELECT g_1.name AS c_0 FROM
> opportunities_small g_1 UNION ALL SELECT g_0.name AS c_0 FROM opportunities
> g_0) X__) v_0 GROUP BY v_0.c_0 ORDER BY v_0.c_0
> Error:
> Invalid table alias or column reference 'v_0': (possible column names are: c_0)
--
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
10 years, 12 months
[JBoss JIRA] (TEIID-2800) Teiid Login Issue with special characters
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2800?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2800.
-----------------------------------
Resolution: Done
Changed the TeiidDataSource logic to pass properties directly rather than reparsing them to avoid going through another encode/decode loop. Also ensured that the user/password are utilized from getConnection.
As for a workaround, there isn't a good one for getConnection - the old logic will ignore the parameters. If the user/password as set as properties without this change they, then they need url encoding.
> Teiid Login Issue with special characters
> -----------------------------------------
>
> Key: TEIID-2800
> URL: https://issues.jboss.org/browse/TEIID-2800
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.1
> Environment: Mainframe Jboss 7.1.1
> Reporter: Gautam Banerjee
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.7
>
>
> When we try to login to teiid programmatically through datasource, we are having problem with username having special characters.
> We are encoding the special character as per url encoding
> eg : username %xyz is encoded as %25xyz but teiid does not decode the special character while passing username. So the username passed by teiid is %25xyz which fails authentication as the actual username is %xyz
--
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
10 years, 12 months