[JBoss JIRA] (TEIID-3009) perform projection minimization on with commands
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3009:
-------------------------------------
Summary: perform projection minimization on with commands
Key: TEIID-3009
URL: https://issues.jboss.org/browse/TEIID-3009
Project: Teiid
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
We currently treat the with clause as the creation of a temporary table at a query scope, but we can do projection minimization based upon the referenced columns. This is somewhat tricky with the current planning logic as we must first plan the with clause to determine if it's eligible for pushdown to then plan the main command.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (TEIID-2481) common table (with) push down improvements
by Mark Addleman (JIRA)
[ https://issues.jboss.org/browse/TEIID-2481?page=com.atlassian.jira.plugin... ]
Mark Addleman commented on TEIID-2481:
--------------------------------------
FYI - Our most pressing need is projection minimization
> common table (with) push down improvements
> ------------------------------------------
>
> Key: TEIID-2481
> URL: https://issues.jboss.org/browse/TEIID-2481
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> The general strategy for with pushdown should better handle:
> - a with clause that can be pushed against a source that does not support common table. If a single reference or some other sufficient condition is met then we should just inline the pushdown rather than inhibiting the whole query from pushing down.
> - even if a source supports with pushdown, it may be more performant in some circumstances to inline the common table reference (such as only a single reference). This is complicated slightly by subqueries.
> - alternatively in some situations even if a with clause can be pushed, it may be better to not perform the pushdown -e.g. two separate pushdown accesses to a common table that is expensive to compute (this may need to be hint driven).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (TEIID-3008) limit being pushed even when already in the source query
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3008:
-------------------------------------
Summary: limit being pushed even when already in the source query
Key: TEIID-3008
URL: https://issues.jboss.org/browse/TEIID-3008
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Query Engine
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.8
Limits are being pushed even when already pushed down - this is a regression from TEIID-2878
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (TEIID-3005) Support Kerberos pass-thru to the data source
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3005?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3005:
---------------------------------------
Van can you then update/move these issues as appropriate?
> Support Kerberos pass-thru to the data source
> ---------------------------------------------
>
> Key: TEIID-3005
> URL: https://issues.jboss.org/browse/TEIID-3005
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Server
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Priority: Critical
>
> Need to add support for Kerberos authentication pass-thru all the way to the data source, for data sources that support Kerberos, of course. Besides relational data sources, could it also support Cloudera Hadoop Distribution.
> This maybe a duplicate of other pass-thru related jira's, but wasn't sure, so I logged this to at least get confirmation.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (TEIID-3005) Support Kerberos pass-thru to the data source
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3005?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3005:
------------------------------------
Based on an email thread, and reply by Martin Simpka:
I'm back from PTO and I got information that entire kerberos to datasource propagation has been deferred to EAP 6.4. However let me know if you are still interested to it.
You can find examples of configuration in README file [1]. Key is to use new org.jboss.security.negotiation.KerberosLoginModule which adds GSSCredential to Subject's privateCredentials. GSSCredential and PasswordCredential are only valid credential interface in JCA.
[1] http://git.app.eng.bos.redhat.com/git/jbossqe-eap-tests-kerberos-datasour...
> Support Kerberos pass-thru to the data source
> ---------------------------------------------
>
> Key: TEIID-3005
> URL: https://issues.jboss.org/browse/TEIID-3005
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Server
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Priority: Critical
>
> Need to add support for Kerberos authentication pass-thru all the way to the data source, for data sources that support Kerberos, of course. Besides relational data sources, could it also support Cloudera Hadoop Distribution.
> This maybe a duplicate of other pass-thru related jira's, but wasn't sure, so I logged this to at least get confirmation.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (TEIID-3005) Support Kerberos pass-thru to the data source
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3005?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3005:
----------------------------------
Assignee: (was: Steven Hawkins)
> Support Kerberos pass-thru to the data source
> ---------------------------------------------
>
> Key: TEIID-3005
> URL: https://issues.jboss.org/browse/TEIID-3005
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Server
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Priority: Critical
>
> Need to add support for Kerberos authentication pass-thru all the way to the data source, for data sources that support Kerberos, of course. Besides relational data sources, could it also support Cloudera Hadoop Distribution.
> This maybe a duplicate of other pass-thru related jira's, but wasn't sure, so I logged this to at least get confirmation.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (TEIID-3005) Support Kerberos pass-thru to the data source
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3005?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3005:
---------------------------------------
So we'll move TEIID-3006 and TEIID-3007 to Iron Jacamar if needed - they do have JBJCA-1157 however there are no comments nor commits so it's unclear what that does.
Then if any of our resource adapters beyond ws need support, then we'll add additional subtasks.
> Support Kerberos pass-thru to the data source
> ---------------------------------------------
>
> Key: TEIID-3005
> URL: https://issues.jboss.org/browse/TEIID-3005
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Server
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Critical
>
> Need to add support for Kerberos authentication pass-thru all the way to the data source, for data sources that support Kerberos, of course. Besides relational data sources, could it also support Cloudera Hadoop Distribution.
> This maybe a duplicate of other pass-thru related jira's, but wasn't sure, so I logged this to at least get confirmation.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months