[JBoss JIRA] (TEIID-5123) Osisoft translator - Cannot cast String to Float if value is negative
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5123?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-5123.
---------------------------------
Resolution: Done
> Osisoft translator - Cannot cast String to Float if value is negative
> ---------------------------------------------------------------------
>
> Key: TEIID-5123
> URL: https://issues.jboss.org/browse/TEIID-5123
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.x-6.4
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
> Fix For: 10.1
>
>
> Casting a string containing a negative value (e.g. '-24') to float fails with
> {noformat}com.osisoft.rdsa.RdsaException: [PIOLEDBENT] Cannot convert -24 from String to Single.{noformat}
> This seems to be a bug in Osisoft PI SQL DAS (server-side not the JDBC driver), as connecting to the PI server using Osisoft's SQL Commander and running
> {code:sql}select cast(N'-24' as single){code}
> results in the same error.
> I think the best course of action would be to document this behaviour of the PI server as known issue and NOT work around it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5126) Osisoft translator - SUBSTRING fails when start > string length
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5126?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-5126.
---------------------------------
Resolution: Won't Fix
Based on the KI, I am marking this as Won't fix
> Osisoft translator - SUBSTRING fails when start > string length
> ---------------------------------------------------------------
>
> Key: TEIID-5126
> URL: https://issues.jboss.org/browse/TEIID-5126
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.12.x-6.4
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
> Priority: Minor
> Fix For: 10.1
>
>
> Calling a query such as
> {code:sql}
> SELECT cast(TIMESTAMPVALUE as string), SUBSTRING(TIMESTAMPVALUE, 22, 0) FROM BQT1.SmallA
> {code}
> fails with the following (the length of timestampvalue converted to string is 20):
> {noformat}
> Connector worker process failed for atomic-request=HOiQATHW3fPH.12.0.9: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT TOP 100 cast(g_0.TimestampValue AS String) AS c_0, SUBSTR(cast(g_0.TimestampValue AS String), 22, 0) AS c_1 FROM dvqe..SmallA AS g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_141]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_141]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_141]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy79.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_141]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280)
> 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:1149) [rt.jar:1.8.0_141]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
> Caused by: java.sql.SQLException: [PIOLEDBENT] Arguments are invalid.
> at com.osisoft.jdbc.StatementImpl.executeQuery(StatementImpl.java:360)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.executeQuery(WrappedStatement.java:344)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:119) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> ... 18 more
> Caused by: com.osisoft.rdsa.RdsaException: [PIOLEDBENT] Arguments are invalid.
> at com.osisoft.rdsa.Command.ExecuteReader(Native Method)
> at com.osisoft.rdsa.Command.executeReader(Command.java:79)
> at com.osisoft.jdbc.StatementImpl.executeQuery(StatementImpl.java:356)
> ... 20 more
> {noformat}
> This appears to be an issue with the SUBSTR implementation on the PI server, we are ok with either a workaround or documenting as KI.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5138) JGroups Channel creation in domain mode is invalid
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5138?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-5138.
---------------------------------
Resolution: Done
The domain mode scripts have been updated to reflect above setting.
> JGroups Channel creation in domain mode is invalid
> --------------------------------------------------
>
> Key: TEIID-5138
> URL: https://issues.jboss.org/browse/TEIID-5138
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Critical
> Fix For: 10.1
>
>
> In domain mode configuration where the JGroups channel is configured, it is configured to be used as a separate channel where it would require separate protocol stack, which is also discouraged form. The suggested configuration is to create a forked channel as
> {code}
> <channel name="ee" stack="udp" cluster="ejb">
> <fork name="teiid-cluster"/>
> </channel>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5146) UNION of two similar JOIN queries fails with ASSERTION FAILED error if it contains table function of procedural call with arguments
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5146?page=com.atlassian.jira.plugin... ]
Work on TEIID-5146 started by Steven Hawkins.
---------------------------------------------
> UNION of two similar JOIN queries fails with ASSERTION FAILED error if it contains table function of procedural call with arguments
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-5146
> URL: https://issues.jboss.org/browse/TEIID-5146
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.4
> Reporter: El Fuego
> Assignee: Steven Hawkins
>
> UNION of two similar JOINs containing table function of procedural call with arguments, like:
> {code:sql}SELECT d.col_t2 FROM "ds.test_t1", table(CALL views.pr0("arg1" => col_t1)) x
> JOIN "ds.test_t2" d
> ON true
> --
> UNION
> --
> SELECT d.col_t2 FROM "ds.test_t1", table(CALL views.pr0("arg1" => col_t1)) x
> JOIN "ds.test_t2" d
> ON true{code}
> fails with error:
> {code}2017-11-11 16:16:57,158 ERROR [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue23) wbDLp863MJn9 TEIID30019 Unexpected exception for request wbDLp863MJn9.7: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null
> at org.teiid.core.util.Assertion.failed(Assertion.java:73)
> at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100)
> at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92)
> at org.teiid.common.buffer.TupleBuffer.getBatch(TupleBuffer.java:287)
> at org.teiid.dqp.internal.process.TupleSourceCache$CopyOnReadTupleSource.nextTuple(TupleSourceCache.java:103)
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:394)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> at org.teiid.query.processor.relational.SourceState.prefetch(SourceState.java:211)
> at org.teiid.query.processor.relational.SourceState.rowCountLE(SourceState.java:158)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:227)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
> at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:102)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
> at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:69)
> at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:70)
> at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:84)
> at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:92)
> at org.teiid.query.processor.relational.NestedTableJoinStrategy.process(NestedTableJoinStrategy.java:119)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:235)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
> at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:102)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:150)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
> at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirect(UnionAllNode.java:147)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
> at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:102)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:152)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:115)
> 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:479)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:349)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:275)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284)
> 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)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745){code}
> even if procedure doesn't use that argument at all.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5145) Logged as 'anonymous' when configuring OAuth2 for OData using KeyCloak
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5145?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5145.
-----------------------------------
Fix Version/s: 10.1
Assignee: Madou Coulibaly (was: Steven Hawkins)
Resolution: Done
> Logged as 'anonymous' when configuring OAuth2 for OData using KeyCloak
> ----------------------------------------------------------------------
>
> Key: TEIID-5145
> URL: https://issues.jboss.org/browse/TEIID-5145
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.12.6_3
> Reporter: Madou Coulibaly
> Assignee: Madou Coulibaly
> Fix For: 10.1
>
>
> After configuring OAuth2-Based Security for OData using Red Hat SSO [1], I have noticed, in the audit log file (teiid-audit.log), there is no longer information about this specific user. Indeed, JDV always logs the user as 'anonymous' .
> 10:29:55,132 DEBUG [org.teiid.AUDIT_LOG] (http-127.0.0.1:8080-1) [sample.1, null anonymous USERPASSWORD null null null false] <session.logon-request>
> 10:29:55,141 DEBUG [org.teiid.AUDIT_LOG] (http-127.0.0.1:8080-1) [anonymous@oauth] <session.logon-success>
> 10:29:55,432 DEBUG [org.teiid.AUDIT_LOG] (http-127.0.0.1:8080-1) OOjgSY3H+PdI [anonymous@oauth] <session.logoff>
> [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_data_virtuali...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5146) UNION of two similar JOIN queries fails with ASSERTION FAILED error if it contains table function of procedural call with arguments
by El Fuego (JIRA)
El Fuego created TEIID-5146:
-------------------------------
Summary: UNION of two similar JOIN queries fails with ASSERTION FAILED error if it contains table function of procedural call with arguments
Key: TEIID-5146
URL: https://issues.jboss.org/browse/TEIID-5146
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 9.3.4
Reporter: El Fuego
Assignee: Steven Hawkins
UNION of two similar JOINs containing table function of procedural call with arguments, like:
{code:sql}SELECT d.col_t2 FROM "ds.test_t1", table(CALL views.pr0("arg1" => col_t1)) x
JOIN "ds.test_t2" d
ON true
--
UNION
--
SELECT d.col_t2 FROM "ds.test_t1", table(CALL views.pr0("arg1" => col_t1)) x
JOIN "ds.test_t2" d
ON true{code}
fails with error:
{code}2017-11-11 16:16:57,158 ERROR [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue23) wbDLp863MJn9 TEIID30019 Unexpected exception for request wbDLp863MJn9.7: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null
at org.teiid.core.util.Assertion.failed(Assertion.java:73)
at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100)
at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92)
at org.teiid.common.buffer.TupleBuffer.getBatch(TupleBuffer.java:287)
at org.teiid.dqp.internal.process.TupleSourceCache$CopyOnReadTupleSource.nextTuple(TupleSourceCache.java:103)
at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:394)
at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
at org.teiid.query.processor.relational.SourceState.prefetch(SourceState.java:211)
at org.teiid.query.processor.relational.SourceState.rowCountLE(SourceState.java:158)
at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:227)
at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:102)
at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:69)
at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:70)
at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:84)
at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:92)
at org.teiid.query.processor.relational.NestedTableJoinStrategy.process(NestedTableJoinStrategy.java:119)
at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:235)
at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:102)
at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:150)
at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirect(UnionAllNode.java:147)
at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:102)
at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281)
at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145)
at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:152)
at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:115)
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:479)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:349)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:275)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284)
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)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745){code}
even if procedure doesn't use that argument at all.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5142) General OData error message has extra escaping
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5142?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5142.
-----------------------------------
Fix Version/s: (was: 10.1)
Resolution: Rejected
I should have realized that the escaping is benign. It just looks odd in a browser.
> General OData error message has extra escaping
> ----------------------------------------------
>
> Key: TEIID-5142
> URL: https://issues.jboss.org/browse/TEIID-5142
> Project: Teiid
> Issue Type: Quality Risk
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Minor
>
> Accessing odata4 with an invalid path gives:
> { "error": { "code": "TEIID16020", "message": "TEIID16020 Invalid URL, no vdb name found on the path. It should be in the form of \"http:\/\/<host>[:<port>]\/odata4\/vdbname\/modelname\/...\"" } }
> With extra escaping in the url description.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5145) Logged as 'anonymous' when configuring OAuth2 for OData using KeyCloak
by Madou Coulibaly (JIRA)
Madou Coulibaly created TEIID-5145:
--------------------------------------
Summary: Logged as 'anonymous' when configuring OAuth2 for OData using KeyCloak
Key: TEIID-5145
URL: https://issues.jboss.org/browse/TEIID-5145
Project: Teiid
Issue Type: Bug
Components: OData
Affects Versions: 8.12.12.6_3
Reporter: Madou Coulibaly
Assignee: Steven Hawkins
After configuring OAuth2-Based Security for OData using Red Hat SSO [1], I have noticed, in the audit log file (teiid-audit.log), there is no longer information about this specific user. Indeed, JDV always logs the user as 'anonymous' .
10:29:55,132 DEBUG [org.teiid.AUDIT_LOG] (http-127.0.0.1:8080-1) [sample.1, null anonymous USERPASSWORD null null null false] <session.logon-request>
10:29:55,141 DEBUG [org.teiid.AUDIT_LOG] (http-127.0.0.1:8080-1) [anonymous@oauth] <session.logon-success>
10:29:55,432 DEBUG [org.teiid.AUDIT_LOG] (http-127.0.0.1:8080-1) OOjgSY3H+PdI [anonymous@oauth] <session.logoff>
[1] https://access.redhat.com/documentation/en-us/red_hat_jboss_data_virtuali...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5007) Changes to reduce Teiid in the cloud footprint
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5007?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5007:
---------------------------------------
> container aware auto-sizing
That can largely be satisfied by the logic in an entry point script, such as: https://github.com/shawkins/teiid-openshift-templates/blob/master/server-... - it already has appropriate memory limits.
An additional modification is to add a CPU_LIMIT env parameter, which can be used to set the socket max workers.
We need limit buffer disk usage as well.
> Changes to reduce Teiid in the cloud footprint
> ----------------------------------------------
>
> Key: TEIID-5007
> URL: https://issues.jboss.org/browse/TEIID-5007
> Project: Teiid
> Issue Type: Quality Risk
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.1
>
>
> A Teiid instance even as swarm or springboot needs additional considerations to minimize the runtime footprint. This includes:
> * container aware auto-sizing. Detection of the number of cpus and available memory need refined - there are experimental settings being considered for containerized vms to better report these values and there is logic in WildFly and other projects that attempts better auto-detection. We also need to utilize the memory buffer space more and probably as off-heap space (and ideally direct operations on the serialized data)
> * Subsystems required include JTA, webserver, security, which could be satisfied by slimmer alternative versions - especially if we make new assumptions, such as not utilizing xa transactions.
> * Engine dependencies could be application specific - removing xml/xsl support, geometry support, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months