[JBoss JIRA] (TEIID-2842) Impala/ HIVE2: Unsupported compress file
by Mike LaSpina (JIRA)
[ https://issues.jboss.org/browse/TEIID-2842?page=com.atlassian.jira.plugin... ]
Mike LaSpina commented on TEIID-2842:
-------------------------------------
Ramesh,
The files used and a doc with some instructions can be found here:
https://jaspersoft.egnyte.com/publicController.do?folderName=20140213&fil...
A couple of notes:
1)The doc refers to tsv files as I had to uncompress to make them work - use the .gz versions in the download link
2) Due to poor internet connection, I only included one of the omniture log files, but the example still holds
3) Once uploaded, you can try a 'Describe' in the HUE Implala web interface and get the 'compressed files not supported' error
> Impala/ HIVE2: Unsupported compress file
> -----------------------------------------
>
> Key: TEIID-2842
> URL: https://issues.jboss.org/browse/TEIID-2842
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Impala/HIVE2 with Teiid
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: teiid
> Fix For: 8.7
>
>
> Teiid makes a query call "Describe table" in HiveMetadataProcessor.addTable(....). However, if the table contains compress file, HIVE2 driver would return the following execption:
> {code}
> java.sql.SQLException: AnalysisException: Failed to load metadata for table: default.omniturelogs
> CAUSED BY: TableLoadingException: Failed to load metadata for table:
> omniturelogs
> CAUSED BY: RuntimeException: Compressed text files are not supported: hdfs://localhost.localdomain:8020/user/cloudera/omniturelogs/Omniture.0.tsv.gz
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:161)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:149)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:182)
> at org.apache.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:246)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
> at org.teiid.translator.hive.HiveMetadataProcessor.addTable(HiveMetadataProcessor.java:112)
> at org.teiid.translator.hive.HiveMetadataProcessor.getConnectorMetadata(HiveMetadataProcessor.java:48)
>
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:311)
> ... 155 more
> {code}
> Maybe Teiid should call "DESCRIBE FORMATTED table" for table that contains compress file.
> Reference:
> http://grokbase.com/t/cloudera/impala-user/13b7c9apmx/impala-failed-to-qu...
--
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, 11 months
[JBoss JIRA] (TEIID-2842) Impala/ HIVE2: Unsupported compress file
by Ivan Chan (JIRA)
[ https://issues.jboss.org/browse/TEIID-2842?page=com.atlassian.jira.plugin... ]
Ivan Chan commented on TEIID-2842:
----------------------------------
It maybe related to this issue which they have fixed it in Impala 0.4
https://issues.cloudera.org/browse/IMPALA-14
> Impala/ HIVE2: Unsupported compress file
> -----------------------------------------
>
> Key: TEIID-2842
> URL: https://issues.jboss.org/browse/TEIID-2842
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Impala/HIVE2 with Teiid
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: teiid
> Fix For: 8.7
>
>
> Teiid makes a query call "Describe table" in HiveMetadataProcessor.addTable(....). However, if the table contains compress file, HIVE2 driver would return the following execption:
> {code}
> java.sql.SQLException: AnalysisException: Failed to load metadata for table: default.omniturelogs
> CAUSED BY: TableLoadingException: Failed to load metadata for table:
> omniturelogs
> CAUSED BY: RuntimeException: Compressed text files are not supported: hdfs://localhost.localdomain:8020/user/cloudera/omniturelogs/Omniture.0.tsv.gz
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:161)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:149)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:182)
> at org.apache.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:246)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
> at org.teiid.translator.hive.HiveMetadataProcessor.addTable(HiveMetadataProcessor.java:112)
> at org.teiid.translator.hive.HiveMetadataProcessor.getConnectorMetadata(HiveMetadataProcessor.java:48)
>
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:311)
> ... 155 more
> {code}
> Maybe Teiid should call "DESCRIBE FORMATTED table" for table that contains compress file.
> Reference:
> http://grokbase.com/t/cloudera/impala-user/13b7c9apmx/impala-failed-to-qu...
--
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, 11 months
[JBoss JIRA] (TEIID-2842) Impala/ HIVE2: Unsupported compress file
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2842?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2842:
-------------------------------------
Mike/Ivan, can you give me sample compressed table to test with. I got Coludera-QuickStart-VM installed
> Impala/ HIVE2: Unsupported compress file
> -----------------------------------------
>
> Key: TEIID-2842
> URL: https://issues.jboss.org/browse/TEIID-2842
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Impala/HIVE2 with Teiid
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: teiid
> Fix For: 8.7
>
>
> Teiid makes a query call "Describe table" in HiveMetadataProcessor.addTable(....). However, if the table contains compress file, HIVE2 driver would return the following execption:
> {code}
> java.sql.SQLException: AnalysisException: Failed to load metadata for table: default.omniturelogs
> CAUSED BY: TableLoadingException: Failed to load metadata for table:
> omniturelogs
> CAUSED BY: RuntimeException: Compressed text files are not supported: hdfs://localhost.localdomain:8020/user/cloudera/omniturelogs/Omniture.0.tsv.gz
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:161)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:149)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:182)
> at org.apache.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:246)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
> at org.teiid.translator.hive.HiveMetadataProcessor.addTable(HiveMetadataProcessor.java:112)
> at org.teiid.translator.hive.HiveMetadataProcessor.getConnectorMetadata(HiveMetadataProcessor.java:48)
>
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:311)
> ... 155 more
> {code}
> Maybe Teiid should call "DESCRIBE FORMATTED table" for table that contains compress file.
> Reference:
> http://grokbase.com/t/cloudera/impala-user/13b7c9apmx/impala-failed-to-qu...
--
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, 11 months
[JBoss JIRA] (TEIID-2851) ODATA POST fails if table column is of IDENTITY type (sql server)
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2851?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2851:
-------------------------------------
Thanks, this will help me duplicate it right away.
> ODATA POST fails if table column is of IDENTITY type (sql server)
> -----------------------------------------------------------------
>
> Key: TEIID-2851
> URL: https://issues.jboss.org/browse/TEIID-2851
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.6
> Reporter: Alex Khvatov
> Assignee: Ramesh Reddy
>
> While INSERT into virtual table created from a table that has IDENTITY (autoincrement) feild (in sql server) works if inserted via JDBC, POST to the same table using ODATA fails.
> I am attaching the stack trace we get.
> 09:49:24,010 ERROR [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-5) null TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: No elements match the predicate
> at org.core4j.Enumerable.first(Enumerable.java:125) [core4j-0.5.jar:]
> at org.odata4j.core.OEntities$OEntityImpl.getProperty(OEntities.java:219) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.teiid.odata.ODataSQLBuilder.buildEntityKey(ODataSQLBuilder.java:1005) [classes:]
> at org.teiid.odata.TeiidProducer.createEntity(TeiidProducer.java:172) [classes:]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:124) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:111) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source) [:1.7.0_17]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.7.0_17]
> at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.7.0_17]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_17]
--
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, 11 months
[JBoss JIRA] (TEIID-2851) ODATA POST fails if table column is of IDENTITY type (sql server)
by Alex Khvatov (JIRA)
[ https://issues.jboss.org/browse/TEIID-2851?page=com.atlassian.jira.plugin... ]
Alex Khvatov commented on TEIID-2851:
-------------------------------------
Hi Ramesh,
here is test case:
1. Started out on SQL SERVER 2008
{noformat}
CREATE TABLE [dbo].[Z1_MOB_SPEECH_LOG_D](
[SPEECH_LOG_SURRO_ID] [int] IDENTITY(1,1) NOT NULL,
[SPEECH_TS] [datetime] NULL,
[SPEECH_TYP_DESC] [varchar](100) NULL,
[ACTL_SPEECH_TXT] [varchar](2000) NULL,
[CLEAN_SPEECH_TXT] [varchar](2000) NULL,
[ONE_CLIENT_ID] [int] NULL,
[IMS_PORTAL_USR_ID] [varchar](20) NULL,
[ROW_CRE_TS] [datetime] NOT NULL,
[ROW_CRE_LOGIN_ID] [varchar](30) NOT NULL,
CONSTRAINT [Z1_XPKMOB_SPEECH_LOG_D] PRIMARY KEY CLUSTERED
(
[SPEECH_LOG_SURRO_ID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
{noformat}
2. In TEIID, "Create JDBC Data Connection"
created a JDBC connection using "Microsoft SQL Server 2008 JDBC Driver"
3. In TEIID, "Create Source Model for JDBC Data Connection"
created a source model using wizard to import table design to the source model
4. In TEIID, New "TEIID Metadata Model"
created a view model using wizard to create a base table off the source model table
added a primary key on column SPEECH_LOG_SURRO_ID
5. In TEIID, New "TEIID VDB"
created new TEIID VDB, adding the source model and view model above
deployed VDB to localhost running TEIID/JBOSS EAP
6. Using a REST-Client (SOAP UI)
issued an HTTP POST: http://localhost:8080/odata/vdbTest/vw_test_log.Z3_MOB_SPEECH_LOG_D_I
...using this data row:
{noformat}
{"SPEECH_TS": "2014-02-10T15:00:33.001","SPEECH_TYP_DESC": "type","ACTL_SPEECH_TXT": "desc","CLEAN_SPEECH_TXT": "clean","ONE_CLIENT_ID": "1","IMS_PORTAL_USR_ID": "(97854)(1)","ROW_CRE_TS": "2014-02-10T15:00:33.002","ROW_CRE_LOGIN_ID": "cw"}
{noformat}
ERROR:
{noformat}
09:49:24,010 ERROR [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-5) null TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: No elements match the predicate
{noformat}
****PLEASE NOTE: I can successfully add data through a straight JDBC Connection using this VDB (Insert into...).
Only in an ODATA Call does it fail.
Also note, if I remove the IDENTITY clause in the SQL Server table, and issue an actual value for the primary key in the data string, the ODATA call works fine.
> ODATA POST fails if table column is of IDENTITY type (sql server)
> -----------------------------------------------------------------
>
> Key: TEIID-2851
> URL: https://issues.jboss.org/browse/TEIID-2851
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.6
> Reporter: Alex Khvatov
> Assignee: Ramesh Reddy
>
> While INSERT into virtual table created from a table that has IDENTITY (autoincrement) feild (in sql server) works if inserted via JDBC, POST to the same table using ODATA fails.
> I am attaching the stack trace we get.
> 09:49:24,010 ERROR [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-5) null TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: No elements match the predicate
> at org.core4j.Enumerable.first(Enumerable.java:125) [core4j-0.5.jar:]
> at org.odata4j.core.OEntities$OEntityImpl.getProperty(OEntities.java:219) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.teiid.odata.ODataSQLBuilder.buildEntityKey(ODataSQLBuilder.java:1005) [classes:]
> at org.teiid.odata.TeiidProducer.createEntity(TeiidProducer.java:172) [classes:]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:124) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:111) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source) [:1.7.0_17]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.7.0_17]
> at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.7.0_17]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_17]
--
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, 11 months
[JBoss JIRA] (TEIID-2851) ODATA POST fails if table column is of IDENTITY type (sql server)
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2851?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2851:
-------------------------------------
Alex, I will see if I can get this into 8.7. Can you attach testcase showing above scenario?
> ODATA POST fails if table column is of IDENTITY type (sql server)
> -----------------------------------------------------------------
>
> Key: TEIID-2851
> URL: https://issues.jboss.org/browse/TEIID-2851
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.6
> Reporter: Alex Khvatov
> Assignee: Ramesh Reddy
>
> While INSERT into virtual table created from a table that has IDENTITY (autoincrement) feild (in sql server) works if inserted via JDBC, POST to the same table using ODATA fails.
> I am attaching the stack trace we get.
> 09:49:24,010 ERROR [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-5) null TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: No elements match the predicate
> at org.core4j.Enumerable.first(Enumerable.java:125) [core4j-0.5.jar:]
> at org.odata4j.core.OEntities$OEntityImpl.getProperty(OEntities.java:219) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.teiid.odata.ODataSQLBuilder.buildEntityKey(ODataSQLBuilder.java:1005) [classes:]
> at org.teiid.odata.TeiidProducer.createEntity(TeiidProducer.java:172) [classes:]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:124) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:111) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
> at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source) [:1.7.0_17]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [rt.jar:1.7.0_17]
> at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.7.0_17]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_17]
--
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, 11 months
[JBoss JIRA] (TEIID-2826) Change build to use zip translator packaging when building jboss kit
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2826?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2826:
---------------------------------------
Just to make sure we're on the same page, the current state simply produces a module with the root being the logical module root org.teiid etc. It's the as kit logic that introduces system/layers/base - I don't think we want that level of knowledge in each of the module builds. If we need to have it that path profile based, that should be easy to do.
Beyond that it seems that your concern is that the EAP/product kit may be different than the community one at an even more granular level. That is a possibility - and one that we have yet to account for even with some current variations (the product security properties files come to mind). If you want to future proof the project directories for that, it should be fine. But at least initially it seems like the module artifacts we're producing should be applicable to both deployments.
> Change build to use zip translator packaging when building jboss kit
> --------------------------------------------------------------------
>
> Key: TEIID-2826
> URL: https://issues.jboss.org/browse/TEIID-2826
> Project: Teiid
> Issue Type: Sub-task
> Components: Build/Kits
> Affects Versions: 8.7
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Change build to use zip translator packaging when building jboss kit
--
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, 11 months
[JBoss JIRA] (TEIID-2826) Change build to use zip translator packaging when building jboss kit
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2826?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2826:
---------------------------------------
> We could compensate for it using a profile based property to adjust the base of the modules directory.
Can you flesh this out a little more? The parent kit build is currently responsible for determining where the module structure should be unzipped.
> The eventual goal if we want move the translators out core Teiid project.
We may still have those projects use the Teiid pom as the parent in any event. So I'd wait before making any more changes.
> Change build to use zip translator packaging when building jboss kit
> --------------------------------------------------------------------
>
> Key: TEIID-2826
> URL: https://issues.jboss.org/browse/TEIID-2826
> Project: Teiid
> Issue Type: Sub-task
> Components: Build/Kits
> Affects Versions: 8.7
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Change build to use zip translator packaging when building jboss kit
--
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, 11 months