December 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2784) ModeShape.vdb deployment issue in server

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2784?page=com.atlassian.jira.plugin... ] Van Halbert closed TEIID-2784. ------------------------------ Resolution: Rejected This is not an issue. I was getting VDB's confused, between one manually deployed and one deployed via Designer. Once that was resolved, there was no issue. > ModeShape.vdb deployment issue in server > ---------------------------------------- > > Key: TEIID-2784 > URL: https://issues.jboss.org/browse/TEIID-2784 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Attachments: ModeShape.vdb > > > When restarting server with attached ModeShape.vdb, get the following server deployment exception (and the VDB require's redeployment to work) > 09:02:43,193 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-12) MSC000001: Failed to start service jboss.deployment.unit."ModeShape.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."ModeShape.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "ModeShape.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for translator > at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.teiid.jboss.TeiidServiceNames.translatorServiceName(TeiidServiceNames.java:65) > at org.teiid.jboss.VDBDeployer.deploy(VDBDeployer.java:169) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > ... 5 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2784) ModeShape.vdb deployment issue in server

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2784?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2784: ------------------------------------- the translator name is not in the VDB that is attached. > ModeShape.vdb deployment issue in server > ---------------------------------------- > > Key: TEIID-2784 > URL: https://issues.jboss.org/browse/TEIID-2784 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Attachments: ModeShape.vdb > > > When restarting server with attached ModeShape.vdb, get the following server deployment exception (and the VDB require's redeployment to work) > 09:02:43,193 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-12) MSC000001: Failed to start service jboss.deployment.unit."ModeShape.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."ModeShape.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "ModeShape.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for translator > at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.teiid.jboss.TeiidServiceNames.translatorServiceName(TeiidServiceNames.java:65) > at org.teiid.jboss.VDBDeployer.deploy(VDBDeployer.java:169) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > ... 5 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2779) Configurable CommonTableExpression support for DB2

by Mark Addleman (JIRA)

[ https://issues.jboss.org/browse/TEIID-2779?page=com.atlassian.jira.plugin... ] Mark Addleman commented on TEIID-2779: -------------------------------------- Ah, that's an interesting twist. I don't have an easy way of testing that right now. Perhaps Andriy can give that a shot. We'll let you know. > Configurable CommonTableExpression support for DB2 > -------------------------------------------------- > > Key: TEIID-2779 > URL: https://issues.jboss.org/browse/TEIID-2779 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 8.5 > Reporter: Andriy Rokhmanov > Assignee: Steven Hawkins > > The LIMIT clause (FETCH FIRST...) inside CTE (WITH...) is not supported on pre-V9 versions of DB2 on z/OS, or new versions of DB2 running in Compatibility Mode. > The CTE support in DB2 translator should be configurable. > See more information: > https://community.jboss.org/thread/235503 -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2779) Configurable CommonTableExpression support for DB2

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2779?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2779: --------------------------------------- I'm thinking of something like: with a as (select * from (select ... fetch first 10 rows only) as x) .... such that you could keep the CTE. The DB2 8 instances (not Z/OS) I have access to is happy with a CTE with a limit, so I'm not directly able to see what doesn't work. > Configurable CommonTableExpression support for DB2 > -------------------------------------------------- > > Key: TEIID-2779 > URL: https://issues.jboss.org/browse/TEIID-2779 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 8.5 > Reporter: Andriy Rokhmanov > Assignee: Steven Hawkins > > The LIMIT clause (FETCH FIRST...) inside CTE (WITH...) is not supported on pre-V9 versions of DB2 on z/OS, or new versions of DB2 running in Compatibility Mode. > The CTE support in DB2 translator should be configurable. > See more information: > https://community.jboss.org/thread/235503 -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2779) Configurable CommonTableExpression support for DB2

by Mark Addleman (JIRA)

[ https://issues.jboss.org/browse/TEIID-2779?page=com.atlassian.jira.plugin... ] Mark Addleman commented on TEIID-2779: -------------------------------------- Yes, we could use an inline view. DB2 seems happier with that syntax. The CTE is just a more convenient syntax. > Configurable CommonTableExpression support for DB2 > -------------------------------------------------- > > Key: TEIID-2779 > URL: https://issues.jboss.org/browse/TEIID-2779 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 8.5 > Reporter: Andriy Rokhmanov > Assignee: Steven Hawkins > > The LIMIT clause (FETCH FIRST...) inside CTE (WITH...) is not supported on pre-V9 versions of DB2 on z/OS, or new versions of DB2 running in Compatibility Mode. > The CTE support in DB2 translator should be configurable. > See more information: > https://community.jboss.org/thread/235503 -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2779) Configurable CommonTableExpression support for DB2

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2779?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2779: --------------------------------------- Is there a chance that different syntax would be helpful here, such as nesting in an inline view? Otherwise I'm thinking that I'll just add a specific override for common table support rather than doing anything with the version. > Configurable CommonTableExpression support for DB2 > -------------------------------------------------- > > Key: TEIID-2779 > URL: https://issues.jboss.org/browse/TEIID-2779 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 8.5 > Reporter: Andriy Rokhmanov > Assignee: Steven Hawkins > > The LIMIT clause (FETCH FIRST...) inside CTE (WITH...) is not supported on pre-V9 versions of DB2 on z/OS, or new versions of DB2 running in Compatibility Mode. > The CTE support in DB2 translator should be configurable. > See more information: > https://community.jboss.org/thread/235503 -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2775) HIVE2: cannot run ORDER BY SQL without LIMIT

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2775?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2775. ----------------------------------- Fix Version/s: 8.7 Resolution: Done Added a doc note about impala options for setting a default limit. > HIVE2: cannot run ORDER BY SQL without LIMIT > --------------------------------------------- > > Key: TEIID-2775 > URL: https://issues.jboss.org/browse/TEIID-2775 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.6 > Environment: Teiid with HIVE2 Impala > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > Fix For: 8.7 > > > Cannot run SQL with order by, but without limit clause. > If I run a sql like the following with HIVE2/ IMPALA: > select "account_type" > from "hive2DS"."accounts" > group by "account_type" > order by "account_type" > Teiid would convert it to: > SELECT g_0.account_type AS c_0 FROM accounts g_0 GROUP BY g_0.account_type ORDER BY c_0 > And I will get the following exception: > [3:51:04 PM] Natalia: org.teiid.jdbc.TeiidSQLException: Error trying to obtain metadata information for the tables that match %: TEIID30489 Unable to load metadata for VDB name > Caused by: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.account_type AS c_0 FROM accounts g_0 GROUP BY g_0.account_type ORDER BY c_0] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:317) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:273) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) > ... 3 more > Caused by: java.sql.SQLException: NotImplementedException: ORDER BY without LIMIT currently not supported > at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:165) > at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:153) > at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:198) > at org.apache.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:300) > at org.apache.hive.jdbc.HivePreparedStatement.executeQuery(HivePreparedStatement.java:106) > at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) > at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) > ... 13 more > Maybe you guys should consider to do order by in memory if LIMIT is not presented for HIVE2 IMPALA. Thanks. > LINK: > http://www.rittmanmead.com/2013/11/connecting-obiee-11-1-1-7-to-cloudera-... -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2773) MATVIEW corrupted after SYSADMIN.refreshMatView()

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2773?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2773: --------------------------------------- Based upon the associated case material this looks like 7.7.x is missing the second commit from TEIID-1956 - https://github.com/teiid/teiid/commit/2c1d37384369e71dc49039b4304d8a20ca3... > MATVIEW corrupted after SYSADMIN.refreshMatView() > ------------------------------------------------- > > Key: TEIID-2773 > URL: https://issues.jboss.org/browse/TEIID-2773 > Project: Teiid > Issue Type: Bug > Components: Query Engine, Server > Affects Versions: 7.7.5 > Environment: EDS 5.3.1 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > > After CALL SYSADMIN.refreshMatView(viewname=>TABLE_NAME, invalidate=>false) against Materialized View, querying "select * from TABLE_NAME", one of columns shows a value of another column. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2784) ModeShape.vdb deployment issue in server

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2784?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2784: ------------------------------------ Something strange is happening then. I see the translator name in the bindings for the vdb. I can deploy from designer and then query it. But if I restart the server, the error occurs. > ModeShape.vdb deployment issue in server > ---------------------------------------- > > Key: TEIID-2784 > URL: https://issues.jboss.org/browse/TEIID-2784 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Attachments: ModeShape.vdb > > > When restarting server with attached ModeShape.vdb, get the following server deployment exception (and the VDB require's redeployment to work) > 09:02:43,193 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-12) MSC000001: Failed to start service jboss.deployment.unit."ModeShape.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."ModeShape.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "ModeShape.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for translator > at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.teiid.jboss.TeiidServiceNames.translatorServiceName(TeiidServiceNames.java:65) > at org.teiid.jboss.VDBDeployer.deploy(VDBDeployer.java:169) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > ... 5 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

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2784) ModeShape.vdb deployment issue in server

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2784?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2784: ------------------------------------- The translator name is blank. Fix and re-deploy > ModeShape.vdb deployment issue in server > ---------------------------------------- > > Key: TEIID-2784 > URL: https://issues.jboss.org/browse/TEIID-2784 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Attachments: ModeShape.vdb > > > When restarting server with attached ModeShape.vdb, get the following server deployment exception (and the VDB require's redeployment to work) > 09:02:43,193 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-12) MSC000001: Failed to start service jboss.deployment.unit."ModeShape.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."ModeShape.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "ModeShape.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for translator > at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.teiid.jboss.TeiidServiceNames.translatorServiceName(TeiidServiceNames.java:65) > at org.teiid.jboss.VDBDeployer.deploy(VDBDeployer.java:169) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > ... 5 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

11 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2013