[JBoss JIRA] (TEIID-3470) NPE in ConnectorWorkItem when using source hints
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3470?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3470:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1238257, https://bugzilla.redhat.com/show_bug.cgi?id=1238429, https://bugzilla.redhat.com/show_bug.cgi?id=1246124 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1238257, https://bugzilla.redhat.com/show_bug.cgi?id=1238429)
> NPE in ConnectorWorkItem when using source hints
> ------------------------------------------------
>
> Key: TEIID-3470
> URL: https://issues.jboss.org/browse/TEIID-3470
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.5
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
> Fix For: 8.7.1.6_2, 8.11, 8.7.4
>
>
> When using a source general source hint in a query that uses multple sources, I get an NPE:
> java.lang.NullPointerException
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.<init>(ConnectorWorkItem.java:141)
> at org.teiid.dqp.internal.datamgr.ConnectorManager.registerRequest(ConnectorManager.java:203)
> at org.teiid.dqp.internal.process.DataTierManagerImpl.registerRequest(DataTierManagerImpl.java:966)
> at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:179)
> at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:475)
> at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:248)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.JoinStrategy.openLeft(JoinStrategy.java:95)
> at org.teiid.query.processor.relational.JoinNode.open(JoinNode.java:145)
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
> at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254)
> at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:136)
> at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:231)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:457)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:298)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:175)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260)
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:173)
> at com.sun.proxy.$Proxy14.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:661)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:527)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3562) Teradata15 - teiid shifts date/time/timestamp values according to timezone.
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3562?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3562.
-----------------------------------
Fix Version/s: 8.12
Resolution: Done
Added logic to not shift time values for teradata literals. With the database timezone set I now see consistent values.
> Teradata15 - teiid shifts date/time/timestamp values according to timezone.
> ---------------------------------------------------------------------------
>
> Key: TEIID-3562
> URL: https://issues.jboss.org/browse/TEIID-3562
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Environment: teradata version - 15.00.01.01
> teradata driver version - 15.10.00.05
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Fix For: 8.12
>
> Attachments: Main.java, out_GMT+0500, out_GMT_not_set
>
>
> Teiid shifts date/time/timestamp values returned from teradata according to user.timezone value [1], [2]. However, when I execute source-specific command, teradata returns correct values [3].
> [1]
> *Query:* SELECT * FROM smalla ORDER BY IntKey
> *-Duser.timezone:* GMT+5
> *Result:*
> || IntKey || DateValue || TimeValue || TimeStampValue ||
> |0 | 1999-12-31 | 19:00:00 | 1999-12-31 19:00:00.0|
> |1 | 2000-01-01 | 20:00:00 | 1999-12-31 19:00:01.0|
> |2 | 2000-01-02 | 21:00:00 | 1999-12-31 19:00:02.0|
> |3 | 2000-01-03 | 22:00:00 | 1999-12-31 19:00:03.0|
> |...|...|...|...|
> [2]
> *Query:* SELECT * FROM smalla ORDER BY IntKey
> *-Duser.timezone:* GMT+1
> *Result:*
> || IntKey || DateValue || TimeValue || TimeStampValue ||
> |0 | 1999-12-31 | 23:00:00 | 1999-12-31 23:00:00.0|
> |1 | 2000-01-01 | 00:00:00 | 1999-12-31 23:00:01.0|
> |2 | 2000-01-02 | 01:00:00 | 1999-12-31 23:00:02.0|
> |3 | 2000-01-03 | 02:00:00 | 1999-12-31 23:00:03.0|
> |...|...|...|...|
> [3]
> *Query:* SELECT g_0.IntKey AS c_0, g_0.DateValue AS c_1, g_0.TimeValue AS c_2, g_0.TimestampValue AS c_3 FROM smalla AS g_0 ORDER BY 1
> *local timezone:* GMT+1/GMT+5
> *Result:*
> || c_0 || c_1 || c_2 || c_3 ||
> |0 | 2000-01-01 | 00:00:00 | 2000-01-01 00:00:00.0|
> |1 | 2000-01-02 | 01:00:00 | 2000-01-01 00:00:01.0|
> |2 | 2000-01-03 | 02:00:00 | 2000-01-01 00:00:02.0|
> |3 | 2000-01-04 | 03:00:00 | 2000-01-01 00:00:03.0|
> |...|...|...|...|
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3492) Provide a mechanism for users to modify the salesforce api version
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3492?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3492.
---------------------------------
Resolution: Done
Rearranged the salesforce jboss-eap modules to make it feasible to use "slot" mechanism, where multiple partner API versions can be defined. Converted the default version to use this structure.
If user wants to use a different version than 22, provided a template project (which by default build version 34) https://github.com/teiid/salesforce as guide. The user should be easily change few properties and modify it to fit any version they need.
> Provide a mechanism for users to modify the salesforce api version
> ------------------------------------------------------------------
>
> Key: TEIID-3492
> URL: https://issues.jboss.org/browse/TEIID-3492
> Project: Teiid
> Issue Type: Feature Request
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 8.12
>
>
> We should provide a mechanism to easily target a different salesforce api version. We are currently defaulting to v22, which is quite old. The version change must be controlled as the metadata and the sf jars can be incompatible - if you for example build a model from v22, then you must stay on v22, and then recreate the model once you want to move to a later version.
> Currently the update procedure would be to copy/modify the salesforce translator module and have it point to newer wsc and partner api jars (which are java api compatible from what I have seen) and then change the any salesforce resource adapters to use the new api url.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3587) Add ability to load translator module based "slot" classfication
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3587?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3587.
---------------------------------
Labels: Alpha2 (was: )
Resolution: Done
Now one can add translator like
{code}
<translator name="salesforce-34" module="org.jboss.teiid.translator.salesforce" slot="34"/>
{code}
The same can also be used in CLI script
> Add ability to load translator module based "slot" classfication
> ----------------------------------------------------------------
>
> Key: TEIID-3587
> URL: https://issues.jboss.org/browse/TEIID-3587
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 8.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: Alpha2
> Fix For: 8.12
>
>
> Currently translator configuration in the Teiid sub-system can only load from module name, which always points to "main" slot. This configuration needs to be expanded such that user can define a specific "slot" of module to use to load the configured translator
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3578) server becomes unresponsive after running for a while
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3578?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3578:
---------------------------------------
So do we need to change the default asynch logging config to discard then since erroring is not an option?
> server becomes unresponsive after running for a while
> -----------------------------------------------------
>
> Key: TEIID-3578
> URL: https://issues.jboss.org/browse/TEIID-3578
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Attachments: server.log, server_startup.log, stackTrace_TEIID-3578, threaddump.txt
>
>
> Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine.
> [root@BIJDVDev2 ~]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/xvde1 6062016 4601808 1397596 77% /
> none 7619624 0 7619624 0% /dev/shm
> [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM]
> [root@BIJDVDev2 ~]# top
> top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00
> Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie
> Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
> Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers
> Swap: 0k total, 0k used, 0k free, 2887904k cached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months
[JBoss JIRA] (TEIID-3578) server becomes unresponsive after running for a while
by Jorge Herrera (JIRA)
[ https://issues.jboss.org/browse/TEIID-3578?page=com.atlassian.jira.plugin... ]
Jorge Herrera commented on TEIID-3578:
--------------------------------------
I switched from DB logging to file based logging, and the server has been up and responsive since friday. Will keep monitoring. But for now this specific issue seems to be resolved.
> server becomes unresponsive after running for a while
> -----------------------------------------------------
>
> Key: TEIID-3578
> URL: https://issues.jboss.org/browse/TEIID-3578
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
> Attachments: server.log, server_startup.log, stackTrace_TEIID-3578, threaddump.txt
>
>
> Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine.
> [root@BIJDVDev2 ~]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/xvde1 6062016 4601808 1397596 77% /
> none 7619624 0 7619624 0% /dev/shm
> [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM]
> [root@BIJDVDev2 ~]# top
> top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00
> Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie
> Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
> Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers
> Swap: 0k total, 0k used, 0k free, 2887904k cached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 5 months