July 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2481) common table (with) push down improvements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2481?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2481: ---------------------------------- Fix Version/s: 8.9 (was: 8.8) > 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.9 > > > 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)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2932) Datastax: fail to access PortfolioDemo (demo schema that provided by Datastax)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2932?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2932: ---------------------------------- Fix Version/s: 8.9 (was: 8.8) > Datastax: fail to access PortfolioDemo (demo schema that provided by Datastax) > ------------------------------------------------------------------------------- > > Key: TEIID-2932 > URL: https://issues.jboss.org/browse/TEIID-2932 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7 > Environment: Datastax with Teiid 8.7 CR > Reporter: Ivan Chan > Assignee: Steven Hawkins > Fix For: 8.9 > > > Fail to access PortfolioDemo (demo schema that provided by Datastax) and the the following exception: > java.lang.NullPointerException > at org.teiid.metadata.MetadataFactory.addColumn(MetadataFactory.java:204) > at org.teiid.translator.cassandra.CassandraMetadataProcessor.addColumnsToTable(CassandraMetadataProcessor.java:101) > at org.teiid.translator.cassandra.CassandraMetadataProcessor.addTable(CassandraMetadataProcessor.java:63) > at org.teiid.translator.cassandra.CassandraMetadataProcessor.process(CassandraMetadataProcessor.java:50) > at org.teiid.translator.cassandra.CassandraMetadataProcessor.process(CassandraMetadataProcessor.java:42) > at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:915) > at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) > at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > at org.teiid.runtime.EmbeddedServer.loadMetadata(EmbeddedServer.java:685) > at org.teiid.runtime.AbstractVDBDeployer.loadMetadata(AbstractVDBDeployer.java:161) > at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:635) > at org.teiid.runtime.EmbeddedServer.deployVDB(EmbeddedServer.java:547) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3021) Serialization of long sqlexception/warning next chains can lead to oom

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3021?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3021. ----------------------------------- Resolution: Done > Serialization of long sqlexception/warning next chains can lead to oom > ---------------------------------------------------------------------- > > Key: TEIID-3021 > URL: https://issues.jboss.org/browse/TEIID-3021 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.4.3, 8.8 > > > The serialization logic for exception chains is not correct and will output exponentially too many instances of chained exceptions, which can lead to out of memory conditions. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3034) Add support for OData query parameters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3034?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3034: ---------------------------------- Issue Type: Bug (was: Feature Request) Priority: Major (was: Minor) Affects Version/s: 8.4.1 (was: 8.7) > Add support for OData query parameters > -------------------------------------- > > Key: TEIID-3034 > URL: https://issues.jboss.org/browse/TEIID-3034 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: OData > Affects Versions: 8.4.1 > Reporter: Greg MacKinnon > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > There are some OData v2 query parameters that don't appear to work as of Teiid 8.7 (please see teiid forum thread 241566 on this topic). I believe these are all OData v2 conventions. > ?$inlineCount=allpages&$top=N : always returns count = $top > $expand : does not appear to work (but no ostensible error) > $count : "TEIID30088 Unrelated order by column g0.SYSID cannot be used in a SET query, with SELECT DISTINCT, or GROUP BY" occurs using this URI pattern entity/$count , per the OData documentation for using this parameter -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3034) Add support for OData query parameters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3034?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3034. ----------------------------------- Fix Version/s: 8.7.1 8.8 Resolution: Done Added an exception for expand usage. Also removed the order by from a count query. > Add support for OData query parameters > -------------------------------------- > > Key: TEIID-3034 > URL: https://issues.jboss.org/browse/TEIID-3034 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: OData > Affects Versions: 8.7 > Reporter: Greg MacKinnon > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.7.1, 8.8 > > > There are some OData v2 query parameters that don't appear to work as of Teiid 8.7 (please see teiid forum thread 241566 on this topic). I believe these are all OData v2 conventions. > ?$inlineCount=allpages&$top=N : always returns count = $top > $expand : does not appear to work (but no ostensible error) > $count : "TEIID30088 Unrelated order by column g0.SYSID cannot be used in a SET query, with SELECT DISTINCT, or GROUP BY" occurs using this URI pattern entity/$count , per the OData documentation for using this parameter -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2982) Allow to change visibility to a model from imported vdb

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2982?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2982. ----------------------------------- Resolution: Done VDB properties of the form model.visible can be used to control visibility. We'll do more for overrides as needed. This will allow for a minor amount of backwards compatibility. > Allow to change visibility to a model from imported vdb > ------------------------------------------------------- > > Key: TEIID-2982 > URL: https://issues.jboss.org/browse/TEIID-2982 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Query Engine > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > Fix For: 8.9 > > > When a new vdb uses import-vdb, changing(override) visibility to a model from imported vdb would need to hide non-related model to the new vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-3033. -------------------------------- Resolution: Rejected This is not an issue. A Teiid Designer issue will be opened to perform the substitution logic at import time. > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3009) perform projection minimization on with commands

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3009?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3009. ----------------------------------- Resolution: Done The logic here will replace any unused projection with a null value - to keep the definition of the cte consistent. The logic is not quite as clean as I would like as it's done in a preprocessing step in relationalplanner and requires some temp plans and additional runs of ruleassignoutputelements. The optimization is not completely deep. Usage of a CTE in any subquery (including other CTEs) will be seen as required - regardless of whether the subquery will actually exist in the final plan form. We'd need better iterative facilities to do any better as that would currently be quite expensive. This commit also corrected an issue with the assignment of with clauses to pushdown queries. The old code did not deeply check for usage. > 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 > Fix For: 8.9 > > > 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)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3035) Request to add NTLM Security to Web service datasources

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-3035?page=com.atlassian.jira.plugin... ] Debbie Steigner commented on TEIID-3035: ---------------------------------------- I didn't see anything regarding setting the credentials via the config file all I saw was the same page which shows setting it programatically. > Request to add NTLM Security to Web service datasources > ------------------------------------------------------- > > Key: TEIID-3035 > URL: https://issues.jboss.org/browse/TEIID-3035 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Debbie Steigner > > Currently the only Security types we support for Web Service data sources is None, HTTPBasic and WSSecurity can NTLM be added? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3035) Request to add NTLM Security to Web service datasources

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3035?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-3035 at 7/16/14 9:25 AM: ---------------------------------------------------------------- I'm not sure of the flow entirely. Another of their pages implies they will pick up the current nt user if no credentials are set, but then the question is whether that is possible/appropriate. Otherwise if they are trying to flow thru with the login credentials or if there is some kind of ntlm token, that seems like it will require modifications on our part. Presumably if you can set things through the cxf config, you would leave our authentication setting to none. However it's not clear from the cxf pages if the necessary properties can be set via the config on the conduit or if they can only be set programatically. was (Author: shawkins): I'm not sure of the flow entirely. Another of their pages implies they will pick up the current nt user if no credentials are set, but then the question is whether that is possible/appropriate. Otherwise if they are trying to flow thru with the login credentials or if there is some kind of ntlm token, that seems like it will require modifications on our part. Also it's not clear from the cxf pages if the necessary properties can be set via the config on the conduit or if they can only be set programatically. > Request to add NTLM Security to Web service datasources > ------------------------------------------------------- > > Key: TEIID-3035 > URL: https://issues.jboss.org/browse/TEIID-3035 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Debbie Steigner > > Currently the only Security types we support for Web Service data sources is None, HTTPBasic and WSSecurity can NTLM be added? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2014