[JBoss JIRA] (TEIID-4429) Special characters in column names when importing CSV files
by João Matos (JIRA)
João Matos created TEIID-4429:
---------------------------------
Summary: Special characters in column names when importing CSV files
Key: TEIID-4429
URL: https://issues.jboss.org/browse/TEIID-4429
Project: Teiid
Issue Type: Bug
Affects Versions: 9.0.3
Environment: Linux Centos VM, 9.0.3 With WildFly, TEIID Designer 10.1, JBDS 9.1.0 GA
Reporter: João Matos
Assignee: Steven Hawkins
Hi,
I've been dwelling with this problem for quite some time and still can't figure out what is wrong, can you help me out (thanks in advance)? Every time I import a CSV file with TEIID designer, in which the column names contain anything that is not a letter/number/underscore (e.g. a white space), I get the following exception when attempting to preview data:
Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...: org.teiid.metadata.ParseException: TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "new_table ( a [*]b[*] string(" at line 3, column 11.
Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...
at org.teiid.query.parser.QueryParser.parseDDL(QueryParser.java:472)
at org.teiid.metadata.MetadataFactory.parse(MetadataFactory.java:776)
at org.teiid.query.metadata.DDLMetadataRepository.loadMetadata(DDLMetadataRepository.java:40)
at org.teiid.runtime.AbstractVDBDeployer$MetadataRepositoryWrapper.loadMetadata(AbstractVDBDeployer.java:84)
at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55)
at org.teiid.jboss.VDBService$6.run(VDBService.java:398)
at org.teiid.jboss.VDBService$7.run(VDBService.java:449)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "new_table ( a [*]b[*] string(" at line 3, column 11.
Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...
at org.teiid.query.parser.QueryParser.convertParserException(QueryParser.java:214)
... 13 more
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4426) Teiid modules have invalid module descriptor (module.xml)
by Juraj Duráni (JIRA)
[ https://issues.jboss.org/browse/TEIID-4426?page=com.atlassian.jira.plugin... ]
Juraj Duráni commented on TEIID-4426:
-------------------------------------
The newest version is 1.6 (see [sources|http://central.maven.org/maven2/org/jboss/modules/jboss-modules/1...], class org.jboss.modules.xml.ModuleXmlParser). But highest supported version in EAP 6.4 (JDV 6.1, 6.2, 6.3) is 1.3.
Just one more thing. Updating to the newest version isn't answer for everything. Some features have been removed in newer versions, e.g. _configuration_ element. But Teiid uses just "basic" features so I do not think it's a big deal.
> Teiid modules have invalid module descriptor (module.xml)
> ---------------------------------------------------------
>
> Key: TEIID-4426
> URL: https://issues.jboss.org/browse/TEIID-4426
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
> Labels: beta2
> Fix For: 9.1
>
>
> More than half of all modules \[1\] in Teiid layer have invalid module.xml file. Each of them states to use XMLNS for module of version 1.0 (_urn:jboss:module:1.0_), but they use _properties_ element, which is available since 1.1.
> {code:plain|title=\[1\] Affected modules (module:slot)}
> org.jboss.teiid.translator.hbase:main
> org.jboss.teiid.translator.simpledb:main
> org.jboss.teiid.translator.salesforce:main
> org.jboss.teiid.admin:main
> org.jboss.teiid.translator.jpa:main
> org.jboss.teiid.translator.olap:main
> io.swagger:main
> org.jboss.teiid.common-core:main
> com.fasterxml.jackson:main
> com.fasterxml.jackson.dataformat.yaml:main
> org.jboss.teiid.translator.cassandra:main
> org.jboss.teiid.translator.google.api:main
> com.force.api:22
> org.reflections:main
> org.jboss.teiid.translator.google:main
> org.antlr:4.5
> org.jboss.teiid.translator.jdbc:main
> org.osgeo.proj4j:main
> org.apache.xmlbeans:main
> org.apache.olingo:main
> com.google.code.findbugs:main
> org.apache.commons.lang:3.3.2
> org.jboss.teiid.translator.simpledb.api:main
> org.jboss.teiid.translator.mongodb.api:main
> org.jboss.teiid.api:main
> org.jboss.teiid.translator.excel:main
> com.datastax.cassandra.driver.core:main
> com.fasterxml.aalto-xml:main
> org.jboss.teiid:main
> org.jboss.teiid.translator.ldap:main
> org.jboss.teiid.translator.odata:main
> com.facebook.presto:main
> com.vividsolutions.jts:main
> org.jboss.oreva:main
> com.fasterxml.jackson.datatype:main
> nux.nux:main
> org.jboss.teiid.translator.ws:main
> org.jboss.teiid.translator.salesforce:34
> dom4j:main
> org.jboss.teiid.translator.object:main
> org.jboss.teiid.security:main
> org.jboss.teiid.translator.infinispan.cache:main
> org.jboss.teiid.translator.hive:main
> org.jboss.teiid.translator.mongodb:main
> org.jboss.teiid.olingo.common:main
> net.sf.saxon:main
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4418) Pushdown of a correlated with clause contains wrong correlated reference
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4418?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4418.
-----------------------------------
Resolution: Done
Corrected the logic in the RelationalPlanner and the AliasGenerator to ensure that correlated references in with clauses will be handled correctly - however did not fully alter the naming logic so that generated common table/column names will be used.
> Pushdown of a correlated with clause contains wrong correlated reference
> ------------------------------------------------------------------------
>
> Key: TEIID-4418
> URL: https://issues.jboss.org/browse/TEIID-4418
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> A query such as:
> {code}
> select e1, e2 from pm1.g2 where e1 = (with CTE1 as /*+ no_inline */ (SELECT pm1.g2.e1 from pm1.g1) select e1 from CTE1)
> {code}
> will pushdown as:
> {code}
> SELECT g_0.e1, g_0.e2 FROM g2 AS g_0 WHERE g_0.e1 = (WITH CTE1 (e1) AS (SELECT g2.e1 AS expr1 FROM g1 AS g_0) SELECT g_1.e1 FROM CTE1 AS g_1)
> {code}
> Note the incorrect g2.e1 reference.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4422) Impala Translator - add pushdown support for concat and concat_ws functions
by Don Krapohl (JIRA)
[ https://issues.jboss.org/browse/TEIID-4422?page=com.atlassian.jira.plugin... ]
Don Krapohl commented on TEIID-4422:
------------------------------------
Steve,
I am requesting that concat function does support varargs in the translator. I'd also request that the concat_ws be added as well because it allows the concat delimiter.
If I can find a few minutes next week I may pull this story and do a push request if I have time.
Thanks!
Don
> Impala Translator - add pushdown support for concat and concat_ws functions
> ---------------------------------------------------------------------------
>
> Key: TEIID-4422
> URL: https://issues.jboss.org/browse/TEIID-4422
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector
> Affects Versions: 9.0.2
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
>
> As a consumer I need the concat and concat_ws function definitions with matching signatures in line with http://www.cloudera.com/documentation/archive/impala/2-x/2-0-x/topics/imp...
> concat:
> concat(string a, string b...)
> Purpose: Returns a single string representing all the argument values joined together.
> Return type: string
> Usage notes: concat() and concat_ws() are appropriate for concatenating the values of multiple columns within the same row, while group_concat() joins together values from different rows.
> concat_ws:
> concat_ws(string sep, string a, string b...)
> Purpose: Returns a single string representing the second and following argument values joined together, delimited by a specified separator.
> Return type: string
> Usage notes: concat() and concat_ws() are appropriate for concatenating the values of multiple columns within the same row, while group_concat() joins together values from different rows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4421) Teiid Translator per source/version
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4421?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4421:
----------------------------------
Component/s: Embedded
Answering my own question, this is specifically an embedded issue since the translator repository is shared by name.
> Teiid Translator per source/version
> -----------------------------------
>
> Key: TEIID-4421
> URL: https://issues.jboss.org/browse/TEIID-4421
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
>
> Teiid actually uses a single translator to connect to a single source/version. However in the case of translators that auto-configure to the given version it is expected to manage creating new instances when necessary.
> Case reproduced when connecting to 2 DBs, one on SQL Server 2012 and another on SQL Server 2008. The pagination SQL translation of SQL Server 2012 does not work on 2008.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4426) Teiid modules have invalid module descriptor (module.xml)
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4426?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-4426.
---------------------------------
Fix Version/s: 9.1
Resolution: Done
Labels: beta2 (was: )
Updated all modules 1.3
> Teiid modules have invalid module descriptor (module.xml)
> ---------------------------------------------------------
>
> Key: TEIID-4426
> URL: https://issues.jboss.org/browse/TEIID-4426
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
> Labels: beta2
> Fix For: 9.1
>
>
> More than half of all modules \[1\] in Teiid layer have invalid module.xml file. Each of them states to use XMLNS for module of version 1.0 (_urn:jboss:module:1.0_), but they use _properties_ element, which is available since 1.1.
> {code:plain|title=\[1\] Affected modules (module:slot)}
> org.jboss.teiid.translator.hbase:main
> org.jboss.teiid.translator.simpledb:main
> org.jboss.teiid.translator.salesforce:main
> org.jboss.teiid.admin:main
> org.jboss.teiid.translator.jpa:main
> org.jboss.teiid.translator.olap:main
> io.swagger:main
> org.jboss.teiid.common-core:main
> com.fasterxml.jackson:main
> com.fasterxml.jackson.dataformat.yaml:main
> org.jboss.teiid.translator.cassandra:main
> org.jboss.teiid.translator.google.api:main
> com.force.api:22
> org.reflections:main
> org.jboss.teiid.translator.google:main
> org.antlr:4.5
> org.jboss.teiid.translator.jdbc:main
> org.osgeo.proj4j:main
> org.apache.xmlbeans:main
> org.apache.olingo:main
> com.google.code.findbugs:main
> org.apache.commons.lang:3.3.2
> org.jboss.teiid.translator.simpledb.api:main
> org.jboss.teiid.translator.mongodb.api:main
> org.jboss.teiid.api:main
> org.jboss.teiid.translator.excel:main
> com.datastax.cassandra.driver.core:main
> com.fasterxml.aalto-xml:main
> org.jboss.teiid:main
> org.jboss.teiid.translator.ldap:main
> org.jboss.teiid.translator.odata:main
> com.facebook.presto:main
> com.vividsolutions.jts:main
> org.jboss.oreva:main
> com.fasterxml.jackson.datatype:main
> nux.nux:main
> org.jboss.teiid.translator.ws:main
> org.jboss.teiid.translator.salesforce:34
> dom4j:main
> org.jboss.teiid.translator.object:main
> org.jboss.teiid.security:main
> org.jboss.teiid.translator.infinispan.cache:main
> org.jboss.teiid.translator.hive:main
> org.jboss.teiid.translator.mongodb:main
> org.jboss.teiid.olingo.common:main
> net.sf.saxon:main
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4426) Teiid modules have invalid module descriptor (module.xml)
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4426?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-4426:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Teiid modules have invalid module descriptor (module.xml)
> ---------------------------------------------------------
>
> Key: TEIID-4426
> URL: https://issues.jboss.org/browse/TEIID-4426
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
>
> More than half of all modules \[1\] in Teiid layer have invalid module.xml file. Each of them states to use XMLNS for module of version 1.0 (_urn:jboss:module:1.0_), but they use _properties_ element, which is available since 1.1.
> {code:plain|title=\[1\] Affected modules (module:slot)}
> org.jboss.teiid.translator.hbase:main
> org.jboss.teiid.translator.simpledb:main
> org.jboss.teiid.translator.salesforce:main
> org.jboss.teiid.admin:main
> org.jboss.teiid.translator.jpa:main
> org.jboss.teiid.translator.olap:main
> io.swagger:main
> org.jboss.teiid.common-core:main
> com.fasterxml.jackson:main
> com.fasterxml.jackson.dataformat.yaml:main
> org.jboss.teiid.translator.cassandra:main
> org.jboss.teiid.translator.google.api:main
> com.force.api:22
> org.reflections:main
> org.jboss.teiid.translator.google:main
> org.antlr:4.5
> org.jboss.teiid.translator.jdbc:main
> org.osgeo.proj4j:main
> org.apache.xmlbeans:main
> org.apache.olingo:main
> com.google.code.findbugs:main
> org.apache.commons.lang:3.3.2
> org.jboss.teiid.translator.simpledb.api:main
> org.jboss.teiid.translator.mongodb.api:main
> org.jboss.teiid.api:main
> org.jboss.teiid.translator.excel:main
> com.datastax.cassandra.driver.core:main
> com.fasterxml.aalto-xml:main
> org.jboss.teiid:main
> org.jboss.teiid.translator.ldap:main
> org.jboss.teiid.translator.odata:main
> com.facebook.presto:main
> com.vividsolutions.jts:main
> org.jboss.oreva:main
> com.fasterxml.jackson.datatype:main
> nux.nux:main
> org.jboss.teiid.translator.ws:main
> org.jboss.teiid.translator.salesforce:34
> dom4j:main
> org.jboss.teiid.translator.object:main
> org.jboss.teiid.security:main
> org.jboss.teiid.translator.infinispan.cache:main
> org.jboss.teiid.translator.hive:main
> org.jboss.teiid.translator.mongodb:main
> org.jboss.teiid.olingo.common:main
> net.sf.saxon:main
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4426) Teiid modules have invalid module descriptor (module.xml)
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4426?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4426:
-------------------------------------
Yes, 1.3 seems to be latest edition scanning through WildFly modules.
> Teiid modules have invalid module descriptor (module.xml)
> ---------------------------------------------------------
>
> Key: TEIID-4426
> URL: https://issues.jboss.org/browse/TEIID-4426
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> More than half of all modules \[1\] in Teiid layer have invalid module.xml file. Each of them states to use XMLNS for module of version 1.0 (_urn:jboss:module:1.0_), but they use _properties_ element, which is available since 1.1.
> {code:plain|title=\[1\] Affected modules (module:slot)}
> org.jboss.teiid.translator.hbase:main
> org.jboss.teiid.translator.simpledb:main
> org.jboss.teiid.translator.salesforce:main
> org.jboss.teiid.admin:main
> org.jboss.teiid.translator.jpa:main
> org.jboss.teiid.translator.olap:main
> io.swagger:main
> org.jboss.teiid.common-core:main
> com.fasterxml.jackson:main
> com.fasterxml.jackson.dataformat.yaml:main
> org.jboss.teiid.translator.cassandra:main
> org.jboss.teiid.translator.google.api:main
> com.force.api:22
> org.reflections:main
> org.jboss.teiid.translator.google:main
> org.antlr:4.5
> org.jboss.teiid.translator.jdbc:main
> org.osgeo.proj4j:main
> org.apache.xmlbeans:main
> org.apache.olingo:main
> com.google.code.findbugs:main
> org.apache.commons.lang:3.3.2
> org.jboss.teiid.translator.simpledb.api:main
> org.jboss.teiid.translator.mongodb.api:main
> org.jboss.teiid.api:main
> org.jboss.teiid.translator.excel:main
> com.datastax.cassandra.driver.core:main
> com.fasterxml.aalto-xml:main
> org.jboss.teiid:main
> org.jboss.teiid.translator.ldap:main
> org.jboss.teiid.translator.odata:main
> com.facebook.presto:main
> com.vividsolutions.jts:main
> org.jboss.oreva:main
> com.fasterxml.jackson.datatype:main
> nux.nux:main
> org.jboss.teiid.translator.ws:main
> org.jboss.teiid.translator.salesforce:34
> dom4j:main
> org.jboss.teiid.translator.object:main
> org.jboss.teiid.security:main
> org.jboss.teiid.translator.infinispan.cache:main
> org.jboss.teiid.translator.hive:main
> org.jboss.teiid.translator.mongodb:main
> org.jboss.teiid.olingo.common:main
> net.sf.saxon:main
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months