[JBoss JIRA] (TEIID-3843) SAP HANA wrong results from MOD with float argument
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3843?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3843:
---------------------------------------
[~tejones] is this something that should still be left open, or should we just remove pushdown support for mod?
> SAP HANA wrong results from MOD with float argument
> ---------------------------------------------------
>
> Key: TEIID-3843
> URL: https://issues.jboss.org/browse/TEIID-3843
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.2.6_2
> Reporter: Jan Stastny
> Assignee: Ted Jones
>
> SAP HANA doesn't handle correctly MOD function with float arguments. The problem occurs when the float value is less than zero.
> According to SAP HANA documentation, its MOD implementation follows the symmetric handling of MOD on less than zero values. In such case, the resulting value should be computed as:
> a is negative whole number
> n is positive whole number
> mod(a,n)
> # get -1*a
> # compute mod(-1*a,n)
> # multiply the result by -1
> # result is -1*mod(-1*a,n)
> SAP HANA follows this rule for other numeric types than float. For example for Long value -24 MOD(-24,11)=-2 , which is correct according to the MOD definition.
> But when you call MOD(-24.0,11) you get 2.0
> In current state, the only thing Teiid could do is to prevent pushing MOD with float arguments. It helps to cast explicitly the column to double.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-3746) Add ETL functionality to Teiid
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3746?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-3746:
-------------------------------------
Fix Version/s: Open To Community
Assignee: (was: Steven Hawkins)
Moving to an open community issue to flesh out more what features are desired. Other relevant issues are TEIID-4155 for scheduling and TEIID-4526 for debezium integration.
> Add ETL functionality to Teiid
> ------------------------------
>
> Key: TEIID-3746
> URL: https://issues.jboss.org/browse/TEIID-3746
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Jérôme Fenal
> Fix For: Open To Community
>
>
> Teeid can offer schema discovery, schema creation, data massaging from one format to another, and handle writes.
> ETL is all about that:
> - Extract
> - Tranform
> - Load
> in batch mode.
> With the dawn of batch mode in JEE7, it could be interesting to add ETL functionality, possibly in the form of a continuous datamover, or a batch datamover, which could also be used in a complete database migration scenario.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4606) Postgresql translator - unable to insert NULL value to column of type Object
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4606?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4606.
---------------------------------
Resolution: Duplicate
Duplicate of TEIID-4607
> Postgresql translator - unable to insert NULL value to column of type Object
> ----------------------------------------------------------------------------
>
> Key: TEIID-4606
> URL: https://issues.jboss.org/browse/TEIID-4606
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.5
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> I have source table (in PostgreSQL) with column of type *bytea*. That table/column is in source model (in Teiid) defined as *blob*. Further, I have one view which casts this column to type *object* (column name is _col1_). In order to be able to insert in such view, I have defined INSTEAD OF TRIGGER (see \[2\]).
> Now I try to insert values into view \[1\]. If col1 is defined in insert statement, everything is OK. However, if col1 is not defined, insert ends with exception \[3\].
> {code:sql|title=Insert}
> insert into a (id) values (1)
> {code}
> {code:xml|title=\[2\] VDB}
> <metadata type="DDL"><![CDATA[
> CREATE FOREIGN TABLE a (id integer PRIMARY KEY, val blob) OPTIONS (UPDATABLE 'TRUE');
> ]]>
> </metadata>
> <metadata type="DDL"><![CDATA[
> CREATE VIEW a (id integer PRIMARY KEY, val object) OPTIONS (UPDATABLE 'TRUE') AS SELECT id, convert(val, object) as val FROM Source.a;
> CREATE TRIGGER ON a INSTEAD OF INSERT AS FOR EACH ROW
> BEGIN ATOMIC
> INSERT INTO Source.a (id, val) VALUES
> (NEW.id, to_bytes(convert(NEW.val, string), 'UTF-8'));
> END;
> </metadata>
> {code}
> {code:plain|Title=\[3\] Exception}
> 13:53:53,359 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue51) Connector worker process failed for atomic-request=b1oXc1KKl6IJ.5.0.17: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11013:TEIID11004 Error executing statement(s): [Prepared Values: [NULL] SQL: INSERT INTO a (id, val) VALUES (1, ?)]
> at org.teiid.translator.jdbc.JDBCUpdateExecution.executeTranslatedCommand(JDBCUpdateExecution.java:293) [translator-jdbc-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.translator.jdbc.JDBCUpdateExecution.execute(JDBCUpdateExecution.java:84) [translator-jdbc-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364)
> at sun.reflect.GeneratedMethodAccessor137.invoke(Unknown Source) [:1.8.0-internal]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0-internal]
> at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0-internal]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy48.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0-internal]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> 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) [rt.jar:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0-internal]
> Caused by: org.postgresql.util.PSQLException: ERROR: column "val" is of type bytea but expression is of type oid
> Hint: You will need to rewrite or cast the expression.
> Position: 36
> at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)
> at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886)
> at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:363)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:493)
> at org.teiid.translator.jdbc.JDBCUpdateExecution.executeTranslatedCommand(JDBCUpdateExecution.java:263) [translator-jdbc-8.12.5.redhat-8.jar:8.12.5.redhat-8]
> ... 19 more
> 13:53:53,363 WARN [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue52) TEIID30020 Processing exception for request b1oXc1KKl6IJ.5 'TEIID30504 Source: 0 TEIID11013:TEIID11004 Error executing statement(s): [Prepared Values: [NULL] SQL: INSERT INTO a (id, val) VALUES (1, ?)]'. Originally TeiidProcessingException 'ERROR: column "val" is of type bytea but expression is of type oid
> Hint: You will need to rewrite or cast the expression.
> Position: 36' QueryExecutorImpl.java:2157. Enable more detailed logging to see the entire stacktrace.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-3280) Embedded Teiid | VDB scoped translators
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3280?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3280:
---------------------------------------
TEIID-4421 added the ability to create translators based upon types/properties with Embedded. That has not yet been extended to vdb scoping.
> Embedded Teiid | VDB scoped translators
> -----------------------------------------
>
> Key: TEIID-3280
> URL: https://issues.jboss.org/browse/TEIID-3280
> Project: Teiid
> Issue Type: Enhancement
> Components: Embedded
> Reporter: Shiveeta Mattoo
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 10.0
>
>
> - Translator instances, once created are applicable for all VDB deployment invocations.
> - Seeking support for VDB scoped translators which could enable configuring properties for translators specific to VDB instances.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-3935) Add option to delay starting the executing of materialization for a period of time (secs)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3935?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3935.
-----------------------------------
Resolution: Out of Date
Marking as out of date given that there has been no push for this and there were other options to explore.
> Add option to delay starting the executing of materialization for a period of time (secs)
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-3935
> URL: https://issues.jboss.org/browse/TEIID-3935
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 8.12.x
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Minor
>
> The problem is, the creation/binding into jndi is done via a web applicatio, but Teiid is starting the materialization execution before all resources are started as part of the JBoss AS server boot up. Would like an option to delay the starting of the materialization execution by "x" amount of seconds.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4065) Accumulo encoding property is effectively unused
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4065?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4065.
-----------------------------------
Fix Version/s: 9.3
Assignee: Steven Hawkins
Resolution: Done
Removed the property and references to it.
> Accumulo encoding property is effectively unused
> ------------------------------------------------
>
> Key: TEIID-4065
> URL: https://issues.jboss.org/browse/TEIID-4065
> Project: Teiid
> Issue Type: Quality Risk
> Components: Misc. Connectors
> Affects Versions: 9.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.3
>
>
> With the use of lexi coders the translator encoding property is effectively unused - however it may be needed if we want to offer a backwards compatible way of accessing older Teiid accumulo data. For older versions everything would need to be typed as string, but we defaulted to the system encoding rather than utf-8, which is what is expected by the string lexicoder.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months