[JBoss JIRA] (TEIID-3849) Writes using Cassandra connector are very slow
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3849?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3849.
-----------------------------------
Resolution: Done
Implemented the update enhancements which check the connection for v2 support. Also updated to use the asynch api - except for the result set, which could be added if needed.
The batching is currently implemented in a single call, but that may need to be split depending upon the volume that is being written.
> Writes using Cassandra connector are very slow
> ----------------------------------------------
>
> Key: TEIID-3849
> URL: https://issues.jboss.org/browse/TEIID-3849
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Pranav K
> Assignee: Steven Hawkins
> Fix For: 9.0
>
>
> The connector seems to execute the insert queries one by one rather than using batched approach, also the API used is the synchronous one instead of the future based async API [session.executeAsync()]
> Cassandra writes are generally very fast, but it was noted in one scenario that on a single node Cassandra setup inserting a set 50k records and 3 columns took more than 25 mins.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIID-3858) Planning error with unrelated sort columns and view removal
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3858?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3858.
-----------------------------------
Resolution: Done
Resolved by preventing the view removal.
> Planning error with unrelated sort columns and view removal
> -----------------------------------------------------------
>
> Key: TEIID-3858
> URL: https://issues.jboss.org/browse/TEIID-3858
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.13, 8.12.3
>
>
> There is an array index out of bounds in rule merge virtual correct order by when there is an unrelated sort over a query with a grouping:
> select a from (SELECT intkey as a, stringkey as b FROM BQT1.SmallA group by intkey, stringkey union all SELECT intkey as a, stringkey as b FROM BQT1.Smallb group by intkey, stringkey) as v order by b
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIID-3858) Planning error with unrelated sort columns and view removal
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3858?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3858:
----------------------------------
Description:
There is an array index out of bounds in rule merge virtual correct order by when there is an unrelated sort over a query with a grouping:
select a from (SELECT intkey as a, stringkey as b FROM BQT1.SmallA group by intkey, stringkey union all SELECT intkey as a, stringkey as b FROM BQT1.Smallb group by intkey, stringkey) as v order by b
was:
There is an array index out of bounds in rule merge virtual correct order by when there is an unrelated sort over a union:
select a from (SELECT intkey as a, stringkey as b FROM BQT1.SmallA group by intkey, stringkey union all SELECT intkey as a, stringkey as b FROM BQT1.Smallb group by intkey, stringkey) as v order by b
Summary: Planning error with unrelated sort columns and view removal (was: Planning error with union and unrelated sort columns)
> Planning error with unrelated sort columns and view removal
> -----------------------------------------------------------
>
> Key: TEIID-3858
> URL: https://issues.jboss.org/browse/TEIID-3858
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.13, 8.12.3
>
>
> There is an array index out of bounds in rule merge virtual correct order by when there is an unrelated sort over a query with a grouping:
> select a from (SELECT intkey as a, stringkey as b FROM BQT1.SmallA group by intkey, stringkey union all SELECT intkey as a, stringkey as b FROM BQT1.Smallb group by intkey, stringkey) as v order by b
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIID-3854) Impala translator - ORDER BY clause using incorrect columns when not in SELECT list
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3854?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3854.
-----------------------------------
Resolution: Done
Resolved by removing support for unrelated order by so that order by columns will always reference the select clause.
> Impala translator - ORDER BY clause using incorrect columns when not in SELECT list
> -----------------------------------------------------------------------------------
>
> Key: TEIID-3854
> URL: https://issues.jboss.org/browse/TEIID-3854
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.1, 8.12.2
> Environment: Ubuntu Trusty on AWS
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.13, 8.12.3
>
>
> We have a scenario in which users want to see month and day names but the data should be sorted by month and day NUMBER. The translated query comes back sorted the wrong column. Oddly in the ORDER clause the translator uses the month name column alias when we specify the month number, day name when we specify day number.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIID-3858) Planning error with union and unrelated sort columns
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3858:
-------------------------------------
Summary: Planning error with union and unrelated sort columns
Key: TEIID-3858
URL: https://issues.jboss.org/browse/TEIID-3858
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.12
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.13, 8.12.3
There is an array index out of bounds in rule merge virtual correct order by when there is an unrelated sort over a union:
select a from (SELECT intkey as a, stringkey as b FROM BQT1.SmallA group by intkey, stringkey union all SELECT intkey as a, stringkey as b FROM BQT1.Smallb group by intkey, stringkey) as v order by b
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIID-3854) Impala translator - ORDER BY clause using incorrect columns when not in SELECT list
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3854?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3854:
---------------------------------------
The issue stems from the override in the HiveSQLConversionVisitor to strip the table from the column reference in the order by clause. This should normally reference the view, but instead references the select clause, so this is incompatible with the alias generation logic that simply sequentially aliases select columns.
> Impala translator - ORDER BY clause using incorrect columns when not in SELECT list
> -----------------------------------------------------------------------------------
>
> Key: TEIID-3854
> URL: https://issues.jboss.org/browse/TEIID-3854
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.1, 8.12.2
> Environment: Ubuntu Trusty on AWS
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.13, 8.12.3
>
>
> We have a scenario in which users want to see month and day names but the data should be sorted by month and day NUMBER. The translated query comes back sorted the wrong column. Oddly in the ORDER clause the translator uses the month name column alias when we specify the month number, day name when we specify day number.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIID-3832) domain install(run teiid-domain-mode-install.cli) failed
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3832?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-3832:
------------------------------------
verified this fixed in 8.13.0.Alpha2.
> domain install(run teiid-domain-mode-install.cli) failed
> --------------------------------------------------------
>
> Key: TEIID-3832
> URL: https://issues.jboss.org/browse/TEIID-3832
> Project: Teiid
> Issue Type: Sub-task
> Components: Build/Kits
> Affects Versions: 8.13
> Reporter: Kylin Soong
> Assignee: Ramesh Reddy
> Labels: Alpha2
> Fix For: 8.13
>
>
> CLI command
> {code}
> /host=master:reload(restart-servers=true)
> {code}
> execute failed due to some errors.
> h3. Error one
> java.lang.ClassNotFoundException: org.wildfly.clustering.jgroups.ChannelFactory from [Module "org.jboss.teiid:main"
> {code}
> [Server:server-one] Caused by: java.lang.ClassNotFoundException: org.wildfly.clustering.jgroups.ChannelFactory from [Module "org.jboss.teiid:main" from local module loader @621be5d1 (finder: local module finder @573fd745 (roots: /home/kylin/tmp2/teiid-8.13.0.Alpha1-SNAPSHOT/modules,/home/kylin/tmp2/teiid-8.13.0.Alpha1-SNAPSHOT/modules/system/layers/dv,/home/kylin/tmp2/teiid-8.13.0.Alpha1-SNAPSHOT/modules/system/layers/base))]
> [Server:server-two] Caused by: java.lang.ClassNotFoundException: org.wildfly.clustering.jgroups.ChannelFactory from [Module "org.jboss.teiid:main" from local module loader @621be5d1 (finder: local module finder @573fd745 (roots: /home/kylin/tmp2/teiid-8.13.0.Alpha1-SNAPSHOT/modules,/home/kylin/tmp2/teiid-8.13.0.Alpha1-SNAPSHOT/modules/system/layers/dv,/home/kylin/tmp2/teiid-8.13.0.Alpha1-SNAPSHOT/modules/system/layers/base))]
> {code}
> h3. Error two
> Failed to start service jboss.infinispan.teiid-cache.resultset-repl
> {code}
> [Server:server-one] 11:54:59,644 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 70) MSC000001: Failed to start service jboss.infinispan.teiid-cache.resultset-repl.config: org.jboss.msc.service.StartException in service jboss.infinispan.teiid-cache.resultset-repl.config: org.infinispan.commons.CacheConfigurationException: ISPN000343: Must have a transport set in the global configuration in order to define a clustered cache
> [Server:server-one] at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:107)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:745)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [Server:server-one] Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000343: Must have a transport set in the global configuration in order to define a clustered cache
> [Server:server-one] at org.infinispan.configuration.cache.ClusteringConfigurationBuilder.validate(ClusteringConfigurationBuilder.java:115)
> [Server:server-one] at org.infinispan.configuration.cache.ConfigurationBuilder.validate(ConfigurationBuilder.java:187)
> [Server:server-one] at org.infinispan.configuration.cache.ConfigurationBuilder.build(ConfigurationBuilder.java:198)
> [Server:server-one] at org.infinispan.manager.DefaultCacheManager.defineConfiguration(DefaultCacheManager.java:382)
> [Server:server-one] at org.infinispan.manager.DefaultCacheManager.defineConfiguration(DefaultCacheManager.java:344)
> [Server:server-one] at org.jboss.as.clustering.infinispan.DefaultCacheContainer.defineConfiguration(DefaultCacheContainer.java:76)
> [Server:server-one] at org.wildfly.clustering.infinispan.spi.service.ConfigurationBuilder.start(ConfigurationBuilder.java:75)
> [Server:server-one] at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:102)
> [Server:server-one] ... 4 more
> [Server:server-two] 11:54:59,948 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 69) MSC000001: Failed to start service jboss.infinispan.teiid-cache.resultset-repl.config: org.jboss.msc.service.StartException in service jboss.infinispan.teiid-cache.resultset-repl.config: org.infinispan.commons.CacheConfigurationException: ISPN000343: Must have a transport set in the global configuration in order to define a clustered cache
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIID-3856) On Windows while trying to implement teiid-8.13.0.Alpha1 with WildFly removing "/" from jboss.home.dir
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3856?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-3856:
------------------------------------
I have test run teiid-8.13.0.Alpha1-SNAPSHOT-wildfly-server on Windows 7, it works fine, also I think this issue are EAP related, rather than Teiid, start from EAP 6.3 and WildFly 9 it seems be fixed, TEIID-3069 also verified this.
> On Windows while trying to implement teiid-8.13.0.Alpha1 with WildFly removing "/" from jboss.home.dir
> ------------------------------------------------------------------------------------------------------
>
> Key: TEIID-3856
> URL: https://issues.jboss.org/browse/TEIID-3856
> Project: Teiid
> Issue Type: Bug
> Environment: Windows
> Reporter: Hanuman Parihar
> Assignee: Steven Hawkins
> Labels: jboss, teiid
>
> On Windows while trying to implement teiid-8.13.0.Alpha1 with WildFly when I deployed VDB's it is giving file not found exception due to file path doesn't having "/" in absolute path i.e. C:UsershanumanpDesktopteiid-8.13.0.Alpha1
> Caused by: org.h2.jdbc.JdbcSQLException: IO Exception: "java.io.FileNotFoundException: C:UsershanumanpDesktopteiid-8.13.0.Alpha1\teiidfiles\customer-schema.sql (The system cannot find the path specified)"; "C:UsershanumanpDesktopteiid-8.13.0.Alpha1/teiidfiles/customer-schema.sql"; SQL statement:
> RUNSCRIPT FROM 'C:UsershanumanpDesktopteiid-8.13.0.Alpha1/teiidfiles/customer-schema.sql' [90031-173]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:331)
> please refer issue : [https://issues.jboss.org/browse/TEIID-3069] and [https://issues.jboss.org/browse/JBEAP-60] which is exact copy of current issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months