[JBoss JIRA] (TEIID-3642) RhinoScriptEngineFactory be removed in Java 8
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3642?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3642:
------------------------------------
can you post that to the community, would prefer not to continue this discussion on the jira.
> RhinoScriptEngineFactory be removed in Java 8
> ----------------------------------------------
>
> Key: TEIID-3642
> URL: https://issues.jboss.org/browse/TEIID-3642
> Project: Teiid
> Issue Type: Quality Risk
> Components: OData
> Affects Versions: 8.7.1.6_2, 8.12
> Environment: * DV 6.2.0.ER4
> * Java 1.8.0_25
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
>
> RhinoScriptEngineFactory be removed in Java 8, this cause OData war deploy output Error:
> {code}
> 09:30:51,315 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-6) JBAS015868: Deployment "deployment.teiid-odata-8.7.1.6_2-redhat-2.war" is using an unsupported module ("org.joda.time:main") which may be changed or removed in future versions without notice.
> 09:30:51,424 ERROR [stderr] (MSC service thread 1-6) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,429 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,505 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,513 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,583 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> {code}
> *OData war* depend on *org.joda.time*, *org.joda.time* depend on *RhinoScriptEngineFactory*, due to RhinoScriptEngineFactory be removed in Java 8, so stderr output in console.
> h3. how to reproduce
> Start DV 6.2 with Java 8.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3642) RhinoScriptEngineFactory be removed in Java 8
by jie tao (JIRA)
[ https://issues.jboss.org/browse/TEIID-3642?page=com.atlassian.jira.plugin... ]
jie tao commented on TEIID-3642:
--------------------------------
thx. this error disappear, but I got: WARN [org.teiid.SECURITY] (New I/O worker #11) null TEIID40011 Processing exception 'TEIID50072 The username "user" and/or password and/or payload token could not be authenticated by security domain teiid-security.' for session null. Exception type org.teiid.client.security.LogonException thrown from org.teiid.jboss.JBossSecurityHelper.authenticate(JBossSecurityHelper.java:116). Enable more detailed logging to see the entire stacktrace.
Idea?
> RhinoScriptEngineFactory be removed in Java 8
> ----------------------------------------------
>
> Key: TEIID-3642
> URL: https://issues.jboss.org/browse/TEIID-3642
> Project: Teiid
> Issue Type: Quality Risk
> Components: OData
> Affects Versions: 8.7.1.6_2, 8.12
> Environment: * DV 6.2.0.ER4
> * Java 1.8.0_25
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
>
> RhinoScriptEngineFactory be removed in Java 8, this cause OData war deploy output Error:
> {code}
> 09:30:51,315 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-6) JBAS015868: Deployment "deployment.teiid-odata-8.7.1.6_2-redhat-2.war" is using an unsupported module ("org.joda.time:main") which may be changed or removed in future versions without notice.
> 09:30:51,424 ERROR [stderr] (MSC service thread 1-6) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,429 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,505 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,513 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,583 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> {code}
> *OData war* depend on *org.joda.time*, *org.joda.time* depend on *RhinoScriptEngineFactory*, due to RhinoScriptEngineFactory be removed in Java 8, so stderr output in console.
> h3. how to reproduce
> Start DV 6.2 with Java 8.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3743) Multiple Count Distinct Columns Fails for Impala
by Scott Wallace (JIRA)
[ https://issues.jboss.org/browse/TEIID-3743?page=com.atlassian.jira.plugin... ]
Scott Wallace updated TEIID-3743:
---------------------------------
Description:
Teiid Impala translator incorrectly allows multiple count distinct columns, which fails to execute since it is not supported by Impala.
Per Cloudera documentation:
{quote}By default, Impala only allows a single COUNT(DISTINCT columns) expression in each query.
To produce the same result as multiple COUNT(DISTINCT) expressions, you can use the following technique for queries involving a single table:
select v1.c1 result1, v2.c1 result2 from (select count(distinct col1) as c1 from t1) v1 cross join (select count(distinct col2) as c1 from t1) v2;{quote}
The Teiid-Impala translator should ideally rewrite the query as necessary so that the query does not fail executing multiple count distincts against Impala.
was:
Teiid Impala translator incorrectly allows multiple count distinct columns.
Per Cloudera documentation:
{quote}By default, Impala only allows a single COUNT(DISTINCT columns) expression in each query.
To produce the same result as multiple COUNT(DISTINCT) expressions, you can use the following technique for queries involving a single table:
select v1.c1 result1, v2.c1 result2 from (select count(distinct col1) as c1 from t1) v1 cross join (select count(distinct col2) as c1 from t1) v2;{quote}
The Teiid-Impala translator should ideally rewrite the query as necessary so that the query does not fail executing multiple count distincts against Impala.
> Multiple Count Distinct Columns Fails for Impala
> ------------------------------------------------
>
> Key: TEIID-3743
> URL: https://issues.jboss.org/browse/TEIID-3743
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.11.4
> Reporter: Scott Wallace
> Assignee: Steven Hawkins
>
> Teiid Impala translator incorrectly allows multiple count distinct columns, which fails to execute since it is not supported by Impala.
> Per Cloudera documentation:
> {quote}By default, Impala only allows a single COUNT(DISTINCT columns) expression in each query.
> To produce the same result as multiple COUNT(DISTINCT) expressions, you can use the following technique for queries involving a single table:
> select v1.c1 result1, v2.c1 result2 from (select count(distinct col1) as c1 from t1) v1 cross join (select count(distinct col2) as c1 from t1) v2;{quote}
> The Teiid-Impala translator should ideally rewrite the query as necessary so that the query does not fail executing multiple count distincts against Impala.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3743) Multiple Count Distinct Columns Fails for Impala
by Scott Wallace (JIRA)
[ https://issues.jboss.org/browse/TEIID-3743?page=com.atlassian.jira.plugin... ]
Scott Wallace updated TEIID-3743:
---------------------------------
Issue Type: Bug (was: Feature Request)
> Multiple Count Distinct Columns Fails for Impala
> ------------------------------------------------
>
> Key: TEIID-3743
> URL: https://issues.jboss.org/browse/TEIID-3743
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.11.4
> Reporter: Scott Wallace
> Assignee: Steven Hawkins
>
> Teiid Impala translator incorrectly allows multiple count distinct columns.
> Per Cloudera documentation:
> {quote}By default, Impala only allows a single COUNT(DISTINCT columns) expression in each query.
> To produce the same result as multiple COUNT(DISTINCT) expressions, you can use the following technique for queries involving a single table:
> select v1.c1 result1, v2.c1 result2 from (select count(distinct col1) as c1 from t1) v1 cross join (select count(distinct col2) as c1 from t1) v2;{quote}
> The Teiid-Impala translator should ideally rewrite the query as necessary so that the query does not fail executing multiple count distincts against Impala.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3743) Multiple Count Distinct Columns Fails for Impala
by Scott Wallace (JIRA)
Scott Wallace created TEIID-3743:
------------------------------------
Summary: Multiple Count Distinct Columns Fails for Impala
Key: TEIID-3743
URL: https://issues.jboss.org/browse/TEIID-3743
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 8.11.4
Reporter: Scott Wallace
Assignee: Steven Hawkins
Teiid Impala translator incorrectly allows multiple count distinct columns.
Per Cloudera documentation:
{quote}By default, Impala only allows a single COUNT(DISTINCT columns) expression in each query.
To produce the same result as multiple COUNT(DISTINCT) expressions, you can use the following technique for queries involving a single table:
select v1.c1 result1, v2.c1 result2 from (select count(distinct col1) as c1 from t1) v1 cross join (select count(distinct col2) as c1 from t1) v2;{quote}
The Teiid-Impala translator should ideally rewrite the query as necessary so that the query does not fail executing multiple count distincts against Impala.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3642) RhinoScriptEngineFactory be removed in Java 8
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3642?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3642:
------------------------------------
ERROR message won't display in log file once remove com.sun.script.javascript.RhinoScriptEngineFactory inside JBOSS_HOME/modules/system/layers/base/sun/jdk/main/service-loader-resources/META-INF/services/javax.script.ScriptEngineFactory
> RhinoScriptEngineFactory be removed in Java 8
> ----------------------------------------------
>
> Key: TEIID-3642
> URL: https://issues.jboss.org/browse/TEIID-3642
> Project: Teiid
> Issue Type: Quality Risk
> Components: OData
> Affects Versions: 8.7.1.6_2, 8.12
> Environment: * DV 6.2.0.ER4
> * Java 1.8.0_25
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
>
> RhinoScriptEngineFactory be removed in Java 8, this cause OData war deploy output Error:
> {code}
> 09:30:51,315 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-6) JBAS015868: Deployment "deployment.teiid-odata-8.7.1.6_2-redhat-2.war" is using an unsupported module ("org.joda.time:main") which may be changed or removed in future versions without notice.
> 09:30:51,424 ERROR [stderr] (MSC service thread 1-6) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,429 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,505 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,513 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,583 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> {code}
> *OData war* depend on *org.joda.time*, *org.joda.time* depend on *RhinoScriptEngineFactory*, due to RhinoScriptEngineFactory be removed in Java 8, so stderr output in console.
> h3. how to reproduce
> Start DV 6.2 with Java 8.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3642) RhinoScriptEngineFactory be removed in Java 8
by jie tao (JIRA)
[ https://issues.jboss.org/browse/TEIID-3642?page=com.atlassian.jira.plugin... ]
jie tao commented on TEIID-3642:
--------------------------------
I added jdk.nashorn.api.scripting.NashornScriptEngineFactory but still the error javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found. Any help? I use teiid designer at Eclipse Luna and try to preview data with test JDBC connection. my teidd version is 8.11.4
> RhinoScriptEngineFactory be removed in Java 8
> ----------------------------------------------
>
> Key: TEIID-3642
> URL: https://issues.jboss.org/browse/TEIID-3642
> Project: Teiid
> Issue Type: Quality Risk
> Components: OData
> Affects Versions: 8.7.1.6_2, 8.12
> Environment: * DV 6.2.0.ER4
> * Java 1.8.0_25
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
>
> RhinoScriptEngineFactory be removed in Java 8, this cause OData war deploy output Error:
> {code}
> 09:30:51,315 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-6) JBAS015868: Deployment "deployment.teiid-odata-8.7.1.6_2-redhat-2.war" is using an unsupported module ("org.joda.time:main") which may be changed or removed in future versions without notice.
> 09:30:51,424 ERROR [stderr] (MSC service thread 1-6) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,429 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,505 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,513 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 09:30:51,583 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> {code}
> *OData war* depend on *org.joda.time*, *org.joda.time* depend on *RhinoScriptEngineFactory*, due to RhinoScriptEngineFactory be removed in Java 8, so stderr output in console.
> h3. how to reproduce
> Start DV 6.2 with Java 8.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (TEIID-3731) Introduce an alternative protocol to lessen the usage of java serialization
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3731?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3731.
-----------------------------------
Fix Version/s: (was: 9.0)
Resolution: Rejected
In working through the potential issues with this, I'm just going to scrap the work I had started as part of the last round of performance testing. If we were to go down this path, we'll probably want to just have dual schemes rather than trying to insert custom object input/output and reusing the existing writeexternal methods.
> Introduce an alternative protocol to lessen the usage of java serialization
> ---------------------------------------------------------------------------
>
> Key: TEIID-3731
> URL: https://issues.jboss.org/browse/TEIID-3731
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> Even with heavy usage of externalizable there is still an overhead to java serialization blocking and reference tracking. With custom object input/output we can eliminate the need for java serialization with most messages.
> This however would need to work beside the existing java serialization protocol for backwards compatibility.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months