[JBoss JIRA] (TEIID-2863) Allow both gssapi and username/password authentication on the same transport
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2863?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2863:
---------------------------------------
> I am expanding the VDB based properties to take multiple "security-domain" names along with its "types" to define all the allowed authentication mechanisms
Why is there a need for multiple security domains?
> Then we can either introduce or re-purpose a URL connection property for JDBC to define auth-type they want to participate in
A generic URL property won't work for the ODBC case. All we have to go by there is the vdb and username.
> Allow both gssapi and username/password authentication on the same transport
> ----------------------------------------------------------------------------
>
> Key: TEIID-2863
> URL: https://issues.jboss.org/browse/TEIID-2863
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> With GSSAPI support enabled, username/password support on the same transport is effectively disabled. JDBC/ODBC should ideally support both on the same transport.
--
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, 9 months
[JBoss JIRA] (TEIID-2863) Allow both gssapi and username/password authentication on the same transport
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2863?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2863:
-------------------------------------
I am expanding the VDB based properties to take multiple "security-domain" names along with its "types" to define all the allowed authentication mechanisms. Then we can either introduce or re-purpose a URL connection property for JDBC to define auth-type they want to participate in. If any of the defined "security-domains" fall into that category, then Teiid should be able to follow through; else fail.
> Allow both gssapi and username/password authentication on the same transport
> ----------------------------------------------------------------------------
>
> Key: TEIID-2863
> URL: https://issues.jboss.org/browse/TEIID-2863
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> With GSSAPI support enabled, username/password support on the same transport is effectively disabled. JDBC/ODBC should ideally support both on the same transport.
--
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, 9 months
[JBoss JIRA] (TEIID-2358) NullPointer in EnhancedSortMergeJoinStrategy
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2358?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2358:
---------------------------------------
Yes, I'm now able to reproduce this. There should be a fix shortly.
> NullPointer in EnhancedSortMergeJoinStrategy
> --------------------------------------------
>
> Key: TEIID-2358
> URL: https://issues.jboss.org/browse/TEIID-2358
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.5, 8.6
> Reporter: Rakesh Balguri
> Assignee: Steven Hawkins
> Attachments: EnhancedSortMergeJoinStrategyTestCases_Updated.zip
>
>
> java.lang.NullPointerException
> at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy$SingleTupleSource.get(EnhancedSortMergeJoinStrategy.java:79)
> at org.teiid.query.processor.relational.ListNestedSortComparator.compare(ListNestedSortComparator.java:149)
> at org.teiid.query.processor.relational.ListNestedSortComparator.compare(ListNestedSortComparator.java:59)
> at java.util.Collections.indexedBinarySearch(Collections.java:377)
> at java.util.Collections.binarySearch(Collections.java:365)
> at org.teiid.common.buffer.SPage.search(SPage.java:140)
> at org.teiid.common.buffer.STree.find(STree.java:245)
> at org.teiid.common.buffer.TupleBrowser.setPage(TupleBrowser.java:144)
> at org.teiid.common.buffer.TupleBrowser.nextTuple(TupleBrowser.java:203)
> at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.process(EnhancedSortMergeJoinStrategy.java:377)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:202)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:70)
> at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:69)
> at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:82)
> at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:91)
> at org.teiid.query.processor.relational.MergeJoinStrategy.process(MergeJoinStrategy.java:149)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:202)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirect(UnionAllNode.java:90)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
> at org.teiid.query.processor.relational.SourceState.getTupleBuffer(SourceState.java:174)
> at org.teiid.query.processor.relational.SourceState.getRowCount(SourceState.java:127)
> at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.shouldIndex(EnhancedSortMergeJoinStrategy.java:306)
> at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.loadRight(EnhancedSortMergeJoinStrategy.java:253)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:198)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:70)
> at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:69)
> at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:82)
> at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:91)
> at org.teiid.query.processor.relational.MergeJoinStrategy.process(MergeJoinStrategy.java:149)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:202)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirect(UnionAllNode.java:90)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.BatchCollector$BatchProducerTupleSource.nextTuple(BatchCollector.java:89)
> at org.teiid.query.processor.relational.GroupingNode.groupPhase(GroupingNode.java:374)
> at org.teiid.query.processor.relational.GroupingNode.nextBatchDirect(GroupingNode.java:318)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
> at org.teiid.query.processor.relational.SourceState.getTupleBuffer(SourceState.java:174)
> at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.loadLeft(EnhancedSortMergeJoinStrategy.java:229)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:186)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:148)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:146)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:112)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291)
> ... 8 more
--
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, 9 months
[JBoss JIRA] (TEIID-2880) Add login username to source query comment, also session and request Id
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2880?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2880:
----------------------------------
Fix Version/s: 8.7
Component/s: JDBC Connector
Ideally we want to use and a translator property to set an expression to define the comment, with substitution from the executioncontext.
> Add login username to source query comment, also session and request Id
> -----------------------------------------------------------------------
>
> Key: TEIID-2880
> URL: https://issues.jboss.org/browse/TEIID-2880
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector
> Reporter: Rick Wagner
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> The user occasionally has problematic queries and while they can go through the command logs to find some details sometimes under heavy usage the logs are rotated at such a rate that they lose the information.
> Please add the login id, session Id, and request Id to the source query comment.
--
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, 9 months
[JBoss JIRA] (TEIID-2878) Push ORDER/LIMIT for UNION query
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2878?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2878.
-----------------------------------
Fix Version/s: 8.7
Resolution: Done
Added logic in rulepushlimit to push both the limit and the order by through union branches. This is mostly for the case that the limit/order by is supported by the source as we don't yet have a more advanced sorted sublist style processing for the sort above the union.
> Push ORDER/LIMIT for UNION query
> --------------------------------
>
> Key: TEIID-2878
> URL: https://issues.jboss.org/browse/TEIID-2878
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 8.7
>
>
> Better support for queries on unions between different sources. ORDER BY is necessary on the inner queries because otherwise the result set will be truncated too early. ORDER BY can be hardcoded on the inner queries but this limits flexibility. Currently in 8.6 if LIMIT is not hardcoded on inner queries, ORDER BY will be stripped from query.
> {code:sql}
> create view v_items (...) as
> select * from (
> (select item_id, created_at, 'Foo' source from foo.items)
> union all
> (select item_id, created_at, 'Bar' source from bar.items)
> ) x;
> -- Page 1.
> select * from v_items order by created_at desc limit 0, 500;
> -- Page 2.
> select * from v_items order by created_at desc limit 500, 500;
> {code}
--
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, 9 months
[JBoss JIRA] (TEIID-2880) Add login username to source query comment, also session and request Id
by Rick Wagner (JIRA)
Rick Wagner created TEIID-2880:
----------------------------------
Summary: Add login username to source query comment, also session and request Id
Key: TEIID-2880
URL: https://issues.jboss.org/browse/TEIID-2880
Project: Teiid
Issue Type: Feature Request
Reporter: Rick Wagner
Assignee: Steven Hawkins
The user occasionally has problematic queries and while they can go through the command logs to find some details sometimes under heavy usage the logs are rotated at such a rate that they lose the information.
Please add the login id, session Id, and request Id to the source query comment.
--
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, 9 months
[JBoss JIRA] (TEIID-2879) Add more Resource Management
by Rick Wagner (JIRA)
Rick Wagner created TEIID-2879:
----------------------------------
Summary: Add more Resource Management
Key: TEIID-2879
URL: https://issues.jboss.org/browse/TEIID-2879
Project: Teiid
Issue Type: Feature Request
Reporter: Rick Wagner
Assignee: Steven Hawkins
To protect the system sometimes we may need to throttle the queries to ensure it does not exhaust all the existing resources on the server. Resource management is the key to play this role of monitoring and throttling queries. Oracle products offer such a feature for managing the consumption of resources. We have quite a number of (Teiid) profiles running on a big box and we want to ensure no silly queires are hogging on to all the resources and consequently causing issue to others.
Ability to throttle the query by restricting query that uses
1) Too much CPU
2) Too much java heap
3) Long running query
--
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, 9 months
[JBoss JIRA] (TEIID-994) Unable to execute Oracle pipelined table function as procedure
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-994?page=com.atlassian.jira.plugin.... ]
Steven Hawkins updated TEIID-994:
---------------------------------
Fix Version/s: 8.7
Assignee: Steven Hawkins
> Unable to execute Oracle pipelined table function as procedure
> --------------------------------------------------------------
>
> Key: TEIID-994
> URL: https://issues.jboss.org/browse/TEIID-994
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7, Open To Community
>
>
> Oracle pipelined table functions (can be used in Oracle queries as TABLE(...)) that can be put in the FROM clause and used as if they were tables although they are really procedures. We found that we imported this table function, although didn't get it quite right - the result set was wrong, which may just be a deficiency of the JDBC import metadata. We were able to map the proc to a table and execute but when we did we got a PL/SQL error from the db.
> Because this is a proc, we are executing it as a CallableStatement down in the JDBC connector which apparently does not work with DataDirect. I'm not sure how we can detect and do something different but seems like we need to have some metadata (procedure name in source?) that can tell us that this proc needs to be run differently and have the Oracle JDBC Connector deal with this properly.
--
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, 9 months
[JBoss JIRA] (TEIID-2358) NullPointer in EnhancedSortMergeJoinStrategy
by Rakesh Balguri (JIRA)
[ https://issues.jboss.org/browse/TEIID-2358?page=com.atlassian.jira.plugin... ]
Rakesh Balguri updated TEIID-2358:
----------------------------------
Affects Version/s: 8.6
8.5
(was: 8.1)
> NullPointer in EnhancedSortMergeJoinStrategy
> --------------------------------------------
>
> Key: TEIID-2358
> URL: https://issues.jboss.org/browse/TEIID-2358
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.5, 8.6
> Reporter: Rakesh Balguri
> Assignee: Steven Hawkins
> Attachments: EnhancedSortMergeJoinStrategyTestCases_Updated.zip
>
>
> java.lang.NullPointerException
> at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy$SingleTupleSource.get(EnhancedSortMergeJoinStrategy.java:79)
> at org.teiid.query.processor.relational.ListNestedSortComparator.compare(ListNestedSortComparator.java:149)
> at org.teiid.query.processor.relational.ListNestedSortComparator.compare(ListNestedSortComparator.java:59)
> at java.util.Collections.indexedBinarySearch(Collections.java:377)
> at java.util.Collections.binarySearch(Collections.java:365)
> at org.teiid.common.buffer.SPage.search(SPage.java:140)
> at org.teiid.common.buffer.STree.find(STree.java:245)
> at org.teiid.common.buffer.TupleBrowser.setPage(TupleBrowser.java:144)
> at org.teiid.common.buffer.TupleBrowser.nextTuple(TupleBrowser.java:203)
> at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.process(EnhancedSortMergeJoinStrategy.java:377)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:202)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:70)
> at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:69)
> at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:82)
> at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:91)
> at org.teiid.query.processor.relational.MergeJoinStrategy.process(MergeJoinStrategy.java:149)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:202)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirect(UnionAllNode.java:90)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
> at org.teiid.query.processor.relational.SourceState.getTupleBuffer(SourceState.java:174)
> at org.teiid.query.processor.relational.SourceState.getRowCount(SourceState.java:127)
> at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.shouldIndex(EnhancedSortMergeJoinStrategy.java:306)
> at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.loadRight(EnhancedSortMergeJoinStrategy.java:253)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:198)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:70)
> at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:69)
> at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:82)
> at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:91)
> at org.teiid.query.processor.relational.MergeJoinStrategy.process(MergeJoinStrategy.java:149)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:202)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirect(UnionAllNode.java:90)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.BatchCollector$BatchProducerTupleSource.nextTuple(BatchCollector.java:89)
> at org.teiid.query.processor.relational.GroupingNode.groupPhase(GroupingNode.java:374)
> at org.teiid.query.processor.relational.GroupingNode.nextBatchDirect(GroupingNode.java:318)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
> at org.teiid.query.processor.relational.SourceState.getTupleBuffer(SourceState.java:174)
> at org.teiid.query.processor.relational.EnhancedSortMergeJoinStrategy.loadLeft(EnhancedSortMergeJoinStrategy.java:229)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:186)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:148)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:146)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:112)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291)
> ... 8 more
--
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, 9 months