[JBoss JIRA] (TEIID-2702) Deploying google using example google.xml throws exception
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2702?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2702.
---------------------------------
> Deploying google using example google.xml throws exception
> -----------------------------------------------------------
>
> Key: TEIID-2702
> URL: https://issues.jboss.org/browse/TEIID-2702
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.6
>
>
> Trying to deploy google using the example and the BatchSize config property is not recognized, error thrown:
> Caused by: java.lang.NoSuchMethodException: JBAS010474: Method setBatchSize not found
> at org.jboss.as.connector.util.Injection.inject(Injection.java:130)
> at org.jboss.as.connector.util.Injection.inject(Injection.java:83)
> at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$AbstractAS7RaDeployer.initAndInject(AbstractResourceAdapterDeploymentService.java:428)
> ... 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, 8 months
[JBoss JIRA] (TEIID-2559) Add additional make dep hint options
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2559?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2559.
---------------------------------
> Add additional make dep hint options
> ------------------------------------
>
> Key: TEIID-2559
> URL: https://issues.jboss.org/browse/TEIID-2559
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.5
>
>
> make dep hints should support additional options to facilitate TEIID-2249. This includes:
> min - the minimum number of rows to trigger a dependent join full pushdown
> max - the maximum number of rows allowed before rejecting the dependent join (this would apply in both full pushdown and partial non-pushdown scenarios - in the latter though it will likely refer to the number of distinct values)
--
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, 8 months
[JBoss JIRA] (TEIID-2462) WS-Security payload flow through "ws" resource adapter
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2462?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2462.
---------------------------------
> WS-Security payload flow through "ws" resource adapter
> ------------------------------------------------------
>
> Key: TEIID-2462
> URL: https://issues.jboss.org/browse/TEIID-2462
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: cxf, ws-security
> Fix For: 8.4
>
>
> Currently only HTTPBasic security credentials flow through the web services resource adapter from the configured security domain, and authorized Subject.
> It is important to device a mechanism to enable security credentials flow through web services resource adapter for purposes ws-security. The idea is based on the Subject making resource adapter calls, the credential payload needs to be converted into CXF configuration.
--
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, 8 months
[JBoss JIRA] (TEIID-2932) Datastax: fail to access PortfolioDemo (demo schema that provided by Datastax)
by Ivan Chan (JIRA)
Ivan Chan created TEIID-2932:
--------------------------------
Summary: 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
Components: Misc. Connectors
Affects Versions: 8.7
Environment: Datastax with Teiid 8.7 CR
Reporter: Ivan Chan
Assignee: Steven Hawkins
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 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, 8 months
[JBoss JIRA] (TEIID-2922) Extra unique constraint in dynamic vdb schema
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2922?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2922:
---------------------------------------
Mark, did you ever see if there is special handling on the Designer side for MySQL?
We are very lenient currently with constraint names. They are effectively scoped to the table - but not even tracked by name. It may be a good idea though to introduce this restriction.
> Extra unique constraint in dynamic vdb schema
> ---------------------------------------------
>
> Key: TEIID-2922
> URL: https://issues.jboss.org/browse/TEIID-2922
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Affects Versions: 8.4
> Reporter: Mark Drilling
> Assignee: Steven Hawkins
>
> I'm getting an extra Unique Constraint in the dynamic VDB schema - for a MySQL table with only a primary key. See steps to reproduce.
--
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, 8 months
[JBoss JIRA] (TEIID-2902) More incremental join when a limit is present
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2902?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2902:
----------------------------------
Fix Version/s: 8.8
> More incremental join when a limit is present
> ---------------------------------------------
>
> Key: TEIID-2902
> URL: https://issues.jboss.org/browse/TEIID-2902
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> For SQL like:
> SELECT
> t1.column1,
> t2.column1
> FROM
> schema1.table1 t1,
> schema2.table1 t2
> WHERE
> t1.column2=t2.column2
> LIMIT 100
> Teiid may get the whole schema1.table1 content and the whole schema2.table1 content, do the join in memory and then, limit the resultset to 100 records.
> However, I think teiid can fetch smaller set of data then do a join. If the join result set is less than number of rows asking, keep fetching next set of data and do a join until hits the limit number.
--
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, 8 months
[JBoss JIRA] (TEIID-2929) Provide ability define "execution properties" as VDB properties
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2929?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2929:
----------------------------------
Fix Version/s: 8.8
> Provide ability define "execution properties" as VDB properties
> ---------------------------------------------------------------
>
> Key: TEIID-2929
> URL: https://issues.jboss.org/browse/TEIID-2929
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> Currently if user needs to set any execution properties on their connection, with JDBC they can define on the URL or use "SET " statement to issue a query. In ODBC can also use "SET " method.
> However, when working with packaged applications and ODBC or in some situations it may be better to configure these properties VDB wide so that all the connections are using same execution properties.
> This JIRA proposes ability to add execution properties as vdb properties in vdb.xml file.
--
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, 8 months