[JBoss JIRA] (TEIID-2919) BigInteger and BigDecimal datatypes are converted into string in MongoDB translator
by Filip Elias (JIRA)
Filip Elias created TEIID-2919:
----------------------------------
Summary: BigInteger and BigDecimal datatypes are converted into string in MongoDB translator
Key: TEIID-2919
URL: https://issues.jboss.org/browse/TEIID-2919
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.4
Reporter: Filip Elias
Assignee: Steven Hawkins
Fix For: 8.7.1
Description of problem:
BigInteger and BigDecimal datatypes are converted into string in MongoDB translator (MongoDBExecutionFactory.java). User can't use these datatypes in the WHERE clause.
For example
The query:
SELECT IntKey FROM SmallA where BIGINTEGERVALUE > 1
returns no results because BIGINTEGERVALUE > 1 is converted into
{ "BIGINTEGERVALUE" : { "$gt" : "1"}}
but is should be
{ "BIGINTEGERVALUE" : { "$gt" : 1}}
--
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-2918) function invocation failure message refinement
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2918:
-------------------------------------
Summary: function invocation failure message refinement
Key: TEIID-2918
URL: https://issues.jboss.org/browse/TEIID-2918
Project: Teiid
Issue Type: Quality Risk
Reporter: Steven Hawkins
Assignee: Steven Hawkins
TEIID-2584 modified the function invocation exception message, but the invocationtargetexception was used, which does not produce a message.
The server side already attempts to display the root exception with when an exception is logged, so this kind of logic is only needed for the client exception - which we could treat in a similar way to produce a more verbose exception.
--
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-2911) Guard against external entity resolving
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2911?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2911:
---------------------------------------
The initial check-in addresses SQL/XML (including DOMs). We can apply the attached patch to OData4J or we compile it and included it in the war classes if needed. From what I can see other projects also completely disabled DTD, probably to address entity expansion issues. But that was not done yet for us.
> Guard against external entity resolving
> ---------------------------------------
>
> Key: TEIID-2911
> URL: https://issues.jboss.org/browse/TEIID-2911
> Project: Teiid
> Issue Type: Bug
> Components: OData, Query Engine
> Affects Versions: 7.7, 8.4
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.4.2, 8.7
>
> Attachments: org.odata4j.stax2.staximpl.StaxXMLFactoryProvider2.diff
>
>
> if applications that expose RESTEasy XML endpoints, add the following snippet to their web.xml file to disable entity expansion in RESTEasy:
> <context-param>
> <param-name>resteasy.document.expand.entity.references</param-name>
> <param-value>false</param-value>
> </context-param>
> Note that this <context-param> setting has precedence over <init-param>, and will override a contrary setting in an <init-param> element.
> However this is not sufficient for OData as OData4j is responsible for parsing the Atom feed. StaxXMLFactoryProvider2 simply creates XMLInputFactories without any options, thus they will perform external entity resolving by default. An issue will need to be opened against OData4j.
> For SQL/XML, the XMLType input factory needs to disable external entity resolving (via experimentation just setting the relevant property doesn't always work, so like other projects we'll set an XMLResolver, which does work).
--
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-2896) Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-2896?page=com.atlassian.jira.plugin... ]
Debbie Steigner updated TEIID-2896:
-----------------------------------
Attachment: sample
Sample data file
> Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-2896
> URL: https://issues.jboss.org/browse/TEIID-2896
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.7
>
> Attachments: sample, TEIID-2896.patch
>
>
> Current behavior is that data lines too short to fit a fixed width data interpretation produces an error such as "Error: Text parse error: Fixed width line width 35 is smaller than the expected 60 on text line 1 in file:/tmp/file.csv.". The customer's use case is interpreting data files from another application which bundles multiple types of data along with additional descriptive info/metadata about the data contained within the file. As the error is thrown if any lines after the first interpreted line are shorter than the summed value of the fixed width columns, they are unable to query the file. The customer wishes for the ERROR to be suppressed and the query to return the data independent of whether it fits the fixed width criteria and potentially to be able to filter the data being retrieved.
--
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-2911) Guard against external entity resolving
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2911?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2911:
----------------------------------
Attachment: org.odata4j.stax2.staximpl.StaxXMLFactoryProvider2.diff
> Guard against external entity resolving
> ---------------------------------------
>
> Key: TEIID-2911
> URL: https://issues.jboss.org/browse/TEIID-2911
> Project: Teiid
> Issue Type: Bug
> Components: OData, Query Engine
> Affects Versions: 7.7, 8.4
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.4.2, 8.7
>
> Attachments: org.odata4j.stax2.staximpl.StaxXMLFactoryProvider2.diff
>
>
> if applications that expose RESTEasy XML endpoints, add the following snippet to their web.xml file to disable entity expansion in RESTEasy:
> <context-param>
> <param-name>resteasy.document.expand.entity.references</param-name>
> <param-value>false</param-value>
> </context-param>
> Note that this <context-param> setting has precedence over <init-param>, and will override a contrary setting in an <init-param> element.
> However this is not sufficient for OData as OData4j is responsible for parsing the Atom feed. StaxXMLFactoryProvider2 simply creates XMLInputFactories without any options, thus they will perform external entity resolving by default. An issue will need to be opened against OData4j.
> For SQL/XML, the XMLType input factory needs to disable external entity resolving (via experimentation just setting the relevant property doesn't always work, so like other projects we'll set an XMLResolver, which does work).
--
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-2912) Teiid JDBC-ODBC bridge metada import fails from MS Access 2013
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2912?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2912:
----------------------------------
Fix Version/s: 8.7.1
Priority: Major (was: Critical)
Component/s: (was: ODBC)
We'll update the AccessExecutionFactory to default with safer importing defaults.
> Teiid JDBC-ODBC bridge metada import fails from MS Access 2013
> --------------------------------------------------------------
>
> Key: TEIID-2912
> URL: https://issues.jboss.org/browse/TEIID-2912
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.4
> Reporter: Filip Nguyen
> Fix For: 8.7.1
>
> Attachments: server-importKeysFalse.log, server.log, standalone.xml, test-vdb.xml
>
>
> Environment:
> * MS Access 2013
> * Windows 2012 Server
> VDB:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="testVDB" version="1">
> <description>Importer VDB</description>
> <property name="UseConnectorMetadata" value="true" />
> <model name="testAccessModel" type="PHYSICAL" visible="true">
> <source name="testAccessModel" translator-name="jdbc-simple" connection-jndi-name="java:/AccessDS" />
> </model>
> </vdb>
> {code}
> Log exceprt (full log attached):
> {noformat}
> ory] (teiid-async-threads - 4) Driver loaded and instance created:sun.jdbc.odbc.JdbcOdbcDriver@49dd4a28
> 08:32:23,935 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing tables
> 08:32:23,952 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing columns
> 08:32:23,985 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing primary keys
> 08:32:23,985 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (teiid-async-threads - 4) AccessDS: returnConnection(2677c1e5, false) [1/20]
> 08:32:23,985 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB testVDB.1 model "testAccessModel" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: [Microsoft][ODBC Driver Manager] Driver does not support this function
> {noformat}
> Driver (standalone.xml attached):
> {code:xml}
> <datasource jndi-name="java:/AccessDS" pool-name="AccessDS" enabled="true">
> <connection-url>jdbc:odbc:AccessDS</connection-url>
> <driver>odbc</driver>
> <transaction-isolation>TRANSACTION_NONE</transaction-isolation>
> <pool>
> <prefill>false</prefill>
> <use-strict-min>false</use-strict-min>
> <flush-strategy>FailingConnectionOnly</flush-strategy>
> </pool>
> </datasource>
> ...
> <drivers>
> <driver name="odbc" module="sun.jdk">
> <driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
> </driver>
> </drivers>
> {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, 8 months
[JBoss JIRA] (TEIID-2914) Infinispan Connector didn't have the advanced searching option exposed
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2914?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2914:
---------------------------------------
> Now, if this logic is pushed into the translator, it brings a lot of dependencies. And on the other had, if put into the connector, I was thinking the cacheContainerWrapper as the means to expose this info, as the connection has access to this object.
How does it bring in less dependencies in the resource adapter? That is we still have to package both the translator and the resource adapter. Are you thinking about making separate resource adapter instances such that one could be omitted from the kits?
> The user/translator doesn't need to know what's the best option in order to issue a query.
The translator is not the user. Also there are for example numerous jdbc capabilities that can be controlled via translator properties.
> Infinispan Connector didn't have the advanced searching option exposed
> ----------------------------------------------------------------------
>
> Key: TEIID-2914
> URL: https://issues.jboss.org/browse/TEIID-2914
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7, 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> The advanced searching option (i.e, lucene searching) that is defined in the .rar was not being picked up in the connector.
> Also, it was incorrectly defined on the translator, because the translator cannot override how the cache is configured.
--
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-2912) Teiid JDBC-ODBC bridge metada import fails from MS Access 2013
by Filip Nguyen (JIRA)
[ https://issues.jboss.org/browse/TEIID-2912?page=com.atlassian.jira.plugin... ]
Filip Nguyen updated TEIID-2912:
--------------------------------
Priority: Critical (was: Blocker)
> Teiid JDBC-ODBC bridge metada import fails from MS Access 2013
> --------------------------------------------------------------
>
> Key: TEIID-2912
> URL: https://issues.jboss.org/browse/TEIID-2912
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector, ODBC
> Affects Versions: 8.4
> Reporter: Filip Nguyen
> Priority: Critical
> Attachments: server-importKeysFalse.log, server.log, standalone.xml, test-vdb.xml
>
>
> Environment:
> * MS Access 2013
> * Windows 2012 Server
> VDB:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="testVDB" version="1">
> <description>Importer VDB</description>
> <property name="UseConnectorMetadata" value="true" />
> <model name="testAccessModel" type="PHYSICAL" visible="true">
> <source name="testAccessModel" translator-name="jdbc-simple" connection-jndi-name="java:/AccessDS" />
> </model>
> </vdb>
> {code}
> Log exceprt (full log attached):
> {noformat}
> ory] (teiid-async-threads - 4) Driver loaded and instance created:sun.jdbc.odbc.JdbcOdbcDriver@49dd4a28
> 08:32:23,935 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing tables
> 08:32:23,952 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing columns
> 08:32:23,985 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing primary keys
> 08:32:23,985 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (teiid-async-threads - 4) AccessDS: returnConnection(2677c1e5, false) [1/20]
> 08:32:23,985 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB testVDB.1 model "testAccessModel" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: [Microsoft][ODBC Driver Manager] Driver does not support this function
> {noformat}
> Driver (standalone.xml attached):
> {code:xml}
> <datasource jndi-name="java:/AccessDS" pool-name="AccessDS" enabled="true">
> <connection-url>jdbc:odbc:AccessDS</connection-url>
> <driver>odbc</driver>
> <transaction-isolation>TRANSACTION_NONE</transaction-isolation>
> <pool>
> <prefill>false</prefill>
> <use-strict-min>false</use-strict-min>
> <flush-strategy>FailingConnectionOnly</flush-strategy>
> </pool>
> </datasource>
> ...
> <drivers>
> <driver name="odbc" module="sun.jdk">
> <driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
> </driver>
> </drivers>
> {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, 8 months
[JBoss JIRA] (TEIID-2912) Teiid JDBC-ODBC bridge metada import fails from MS Access 2013
by Filip Nguyen (JIRA)
[ https://issues.jboss.org/browse/TEIID-2912?page=com.atlassian.jira.plugin... ]
Filip Nguyen commented on TEIID-2912:
-------------------------------------
You are correct Ramesh. This can be workarounded by using:
{code:xml}
<property name="importer.importKeys" value="false"/>
<property name="importer.excludeTables" value=".*MSys.*"/>
{code}
> Teiid JDBC-ODBC bridge metada import fails from MS Access 2013
> --------------------------------------------------------------
>
> Key: TEIID-2912
> URL: https://issues.jboss.org/browse/TEIID-2912
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector, ODBC
> Affects Versions: 8.4
> Reporter: Filip Nguyen
> Priority: Blocker
> Attachments: server-importKeysFalse.log, server.log, standalone.xml, test-vdb.xml
>
>
> Environment:
> * MS Access 2013
> * Windows 2012 Server
> VDB:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="testVDB" version="1">
> <description>Importer VDB</description>
> <property name="UseConnectorMetadata" value="true" />
> <model name="testAccessModel" type="PHYSICAL" visible="true">
> <source name="testAccessModel" translator-name="jdbc-simple" connection-jndi-name="java:/AccessDS" />
> </model>
> </vdb>
> {code}
> Log exceprt (full log attached):
> {noformat}
> ory] (teiid-async-threads - 4) Driver loaded and instance created:sun.jdbc.odbc.JdbcOdbcDriver@49dd4a28
> 08:32:23,935 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing tables
> 08:32:23,952 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing columns
> 08:32:23,985 DEBUG [org.teiid.CONNECTOR] (teiid-async-threads - 4) JDBCMetadataProcessor - Importing primary keys
> 08:32:23,985 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (teiid-async-threads - 4) AccessDS: returnConnection(2677c1e5, false) [1/20]
> 08:32:23,985 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB testVDB.1 model "testAccessModel" metadata failed to load. Reason:TEIID11010 java.sql.SQLException: [Microsoft][ODBC Driver Manager] Driver does not support this function
> {noformat}
> Driver (standalone.xml attached):
> {code:xml}
> <datasource jndi-name="java:/AccessDS" pool-name="AccessDS" enabled="true">
> <connection-url>jdbc:odbc:AccessDS</connection-url>
> <driver>odbc</driver>
> <transaction-isolation>TRANSACTION_NONE</transaction-isolation>
> <pool>
> <prefill>false</prefill>
> <use-strict-min>false</use-strict-min>
> <flush-strategy>FailingConnectionOnly</flush-strategy>
> </pool>
> </datasource>
> ...
> <drivers>
> <driver name="odbc" module="sun.jdk">
> <driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
> </driver>
> </drivers>
> {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, 8 months
[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-2786:
------------------------------------
I retested using Teiid 8.7 and ModeShape 3.7 and ran across the NumberFormatException above.
I noted on MODE-2125 as to where the issue is in the ModeShape jdbc driver.
> ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-2786
> URL: https://issues.jboss.org/browse/TEIID-2786
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 7.7
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 8.7.1
>
> Attachments: mode.patch
>
>
> When trying to use the Teiid Designer feature of importing using a Teiid Connection fails when the connection is to ModeShape. The following exception:
> 08:33:44,914 ERROR [stderr] (teiid-async-threads - 2) java.sql.SQLFeatureNotSupportedException
> 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.modeshape.jdbc.JcrMetaData.getTypeInfo(JcrMetaData.java:1656)
> 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:107)
> 08:33:44,915 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml")
> 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:280)
> 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:62)
> 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61)
> 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
> 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$6.run(VDBService.java:397)
> 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$7.run(VDBService.java:444)
> 08:33:44,918 ERROR [stderr] (teiid-async-threads - 2) at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
> My guess is the local modeshape jdbc driver hasn't been fully vetted in this area, as the remote JDBC version has been the one used when using the Modeshape eclipse plugin for importing the metadata.
--
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