[JBoss JIRA] (TEIID-5244) Text Based LoginModule does not find properties files
by Bram Gadeyne (JIRA)
Bram Gadeyne created TEIID-5244:
-----------------------------------
Summary: Text Based LoginModule does not find properties files
Key: TEIID-5244
URL: https://issues.jboss.org/browse/TEIID-5244
Project: Teiid
Issue Type: Bug
Affects Versions: 10.1
Reporter: Bram Gadeyne
Assignee: Steven Hawkins
Hi,
I have this in my configuration:
{code:xml}
<security-domain name="teiid-security" cache-type="default">
<authentication>
<login-module code="UsersRoles" flag="required">
<module-option name="usersProperties" value="$(jboss.server.config.dir)/teiid-security-users.properties"/>
<module-option name="rolesProperties" value="$(jboss.server.config.dir)/teiid-security-roles.properties"/>
</login-module>
</authentication>
</security-domain>
{code}
The two files teiid-security-roles.properties and teiid-security-users.properties are located in the configuration directory of wildfly.
I see this error message in the logs: It seems like teiid is using the value as a directory.
2018-02-01 15:20:40,918 ERROR [org.jboss.security] (NIO1) PBOX00261: Failed to load users/passwords/roles files: java.io.IOException: PBOX00072: Properties file $(jboss.server.config.dir)/teiid-security-users.properties/defaultUsers.properties not found
at org.jboss.security.auth.spi.Util.loadProperties(Util.java:212)
at org.jboss.security.auth.spi.UsersRolesLoginModule.loadUsers(UsersRolesLoginModule.java:205)
at org.jboss.security.auth.spi.UsersRolesLoginModule.createUsers(UsersRolesLoginModule.java:219)
at org.jboss.security.auth.spi.UsersRolesLoginModule.initialize(UsersRolesLoginModule.java:146)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5206) Allow exponential values in OData V4 payloads with decimals
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-5206?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-5206:
------------------------------------
[~rareddy] which is the case in here.
9.9999999999E8 moves the decimal point 8 positions to right, which means the result is 999,999,999.99 (I added commas as thousands separator).
And this is the highest value for bigdecimal(11,2), right?
But the validation (after the regex pattern check), doesn't account for the E8 part, effectively complaining, that the value 9.9999999999 doesn't comply to Bigdecimal(11,2) format. But it does, just is written in different way.
> Allow exponential values in OData V4 payloads with decimals
> -----------------------------------------------------------
>
> Key: TEIID-5206
> URL: https://issues.jboss.org/browse/TEIID-5206
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.12.x-6.4
>
>
> This is link to the upstream Olingo issue https://issues.apache.org/jira/browse/OLINGO-1150
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5241) Problem with OData proxy configuration
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5241?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5241:
----------------------------------
Fix Version/s: 10.0.3
9.3.7
10.1.1
> Problem with OData proxy configuration
> --------------------------------------
>
> Key: TEIID-5241
> URL: https://issues.jboss.org/browse/TEIID-5241
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Reporter: Divyesh Vallabh
> Assignee: Steven Hawkins
> Fix For: 10.2, 10.0.3, 9.3.7, 10.1.1
>
>
> When configuring the proxy-base-uri parameter in the web.xml in the teiid-olingo-odata4.war located in the <jbosshome>\modules\system\layers\dv\org\jboss\teiid\main\deployments folder the following error is generated when trying to access a vdb via the OData protocol
> 2018-01-26 11:50:22,396 WARN [org.teiid.ODATA] (default task-2) TEIID16052 Unable to process odata request due to: The URI is malformed.: Unexpected start of resource-path segment.
> at org.apache.olingo.server.core.uri.parser.ResourcePathParser.leadingResourcePathSegment(ResourcePathParser.java:236)
> at org.apache.olingo.server.core.uri.parser.ResourcePathParser.parsePathSegment(ResourcePathParser.java:88)
> at org.apache.olingo.server.core.uri.parser.Parser.parseUri(Parser.java:234)
> at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:93)
> at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:67)
> at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:39)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5241) Problem with OData proxy configuration
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5241?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5241:
---------------------------------------
[~rareddy] what fix releases should this go int?
> Problem with OData proxy configuration
> --------------------------------------
>
> Key: TEIID-5241
> URL: https://issues.jboss.org/browse/TEIID-5241
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Reporter: Divyesh Vallabh
> Assignee: Steven Hawkins
> Fix For: 10.2
>
>
> When configuring the proxy-base-uri parameter in the web.xml in the teiid-olingo-odata4.war located in the <jbosshome>\modules\system\layers\dv\org\jboss\teiid\main\deployments folder the following error is generated when trying to access a vdb via the OData protocol
> 2018-01-26 11:50:22,396 WARN [org.teiid.ODATA] (default task-2) TEIID16052 Unable to process odata request due to: The URI is malformed.: Unexpected start of resource-path segment.
> at org.apache.olingo.server.core.uri.parser.ResourcePathParser.leadingResourcePathSegment(ResourcePathParser.java:236)
> at org.apache.olingo.server.core.uri.parser.ResourcePathParser.parsePathSegment(ResourcePathParser.java:88)
> at org.apache.olingo.server.core.uri.parser.Parser.parseUri(Parser.java:234)
> at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:93)
> at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:67)
> at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:39)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-3843) SAP HANA wrong results from MOD with float argument
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3843?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3843:
------------------------------------------------
Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1284878|https://bugzilla.redhat.com/show_bug.cgi?id=1284878] from ON_QA to CLOSED
> 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.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5243) Embedded SessionService does not monitor sessions
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5243:
-------------------------------------
Summary: Embedded SessionService does not monitor sessions
Key: TEIID-5243
URL: https://issues.jboss.org/browse/TEIID-5243
Project: Teiid
Issue Type: Bug
Components: Embedded
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.2, 10.1.1
Max session age and ping are not enforced with Teiid embedded as the start method is not explicitly called. Ping is only an issue for remote Teiid JDBC in a clustered configuration.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-4694) PrestoDB translator - NULL values not supported in SemiJoin
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4694?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4694:
------------------------------------------------
Andrej Smigala <asmigala(a)redhat.com> changed the Status of [bug 1515761|https://bugzilla.redhat.com/show_bug.cgi?id=1515761] from ON_QA to ASSIGNED
> PrestoDB translator - NULL values not supported in SemiJoin
> -----------------------------------------------------------
>
> Key: TEIID-4694
> URL: https://issues.jboss.org/browse/TEIID-4694
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.8.6_3
> Reporter: Juraj Duráni
> Assignee: Kylin Soong
> Fix For: 9.2
>
>
> PrestoDB does not allows NULL values in SemiJoin operator. It means, that query like \[1\] causes an exception \[2\]. However, this is disallowed in version 0.162 but worked in 0.161. According to GitHub issues \[3\], this will be fixed in one of the future versions of PrestoDB. Do we want to handle it somehow?
> Development and release frequency of PrestoDB seems to be pretty fast (new release every 2 or 3 week).
> {code:sql|title=\[1\] Query}
> SELECT IntKey, ShortValue FROM BQT1.SmallA WHERE BQT1.SmallA.ShortValue IN (SELECT ShortValue FROM BQT1.SmallB)
> {code}
> {code:plain|title=\[2\] Exception}
> org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 Source: Unexpected exception while translating results: Query failed (#20170110_072908_00117_gftb8): NULL values are not allowed on the probe side of SemiJoin operator. See the query plan for details.
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> ...
> Caused by: java.lang.RuntimeException: Remote com.facebook.presto.jdbc.internal.client.FailureInfo$FailureException: NULL values are not allowed on the probe side of SemiJoin operator. See the query plan for details.
> at com.facebook.presto.operator.HashSemiJoinOperator.addInput(HashSemiJoinOperator.java:179)
> at com.facebook.presto.operator.Driver.processInternal(Driver.java:384)
> at com.facebook.presto.operator.Driver.processFor(Driver.java:301)
> at com.facebook.presto.execution.SqlTaskExecution$DriverSplitRunner.processFor(SqlTaskExecution.java:622)
> at com.facebook.presto.execution.TaskExecutor$PrioritizedSplitRunner.process(TaskExecutor.java:534)
> at com.facebook.presto.execution.TaskExecutor$Runner.run(TaskExecutor.java:670)
> ... 3 more
> {code}
> \[3\] https://github.com/prestodb/presto/issues/6991
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (TEIID-5168) PrestoDB translator - Convert to float not pushed correctly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5168?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-5168:
------------------------------------------------
Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1515768|https://bugzilla.redhat.com/show_bug.cgi?id=1515768] from ON_QA to CLOSED
> PrestoDB translator - Convert to float not pushed correctly
> -----------------------------------------------------------
>
> Key: TEIID-5168
> URL: https://issues.jboss.org/browse/TEIID-5168
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.x-6.4
> Reporter: Andrej Šmigala
> Assignee: Steven Hawkins
> Fix For: 10.1, 10.0.2
>
>
> Running query such as
> {code:sql}
> SELECT StringKey, (convert(StringKey, float)+3) FROM BQT1.SmallA
> {code}
> Fails with the following exception:
> {noformat}
> org.teiid.translator.jdbc.JDBCExecutionException: 1 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT g_0.stringkey AS c_0, (g_0.stringkey + 3.0) AS c_1 FROM smalla AS g_0 LIMIT 100]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363)
> at sun.reflect.GeneratedMethodAccessor171.invoke(Unknown Source) [: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.$Proxy80.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: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: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: Query failed (#20171121_110032_00034_8zhqn): line 1:45: '+' cannot be applied to varchar(10), double
> at com.facebook.presto.jdbc.PrestoResultSet.resultsException(PrestoResultSet.java:1799)
> at com.facebook.presto.jdbc.PrestoResultSet.getColumns(PrestoResultSet.java:1747)
> at com.facebook.presto.jdbc.PrestoResultSet.<init>(PrestoResultSet.java:125)
> at com.facebook.presto.jdbc.PrestoStatement.execute(PrestoStatement.java:212)
> at com.facebook.presto.jdbc.PrestoStatement.executeQuery(PrestoStatement.java:69)
> 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-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> ... 17 more
> {noformat}
> The query is translated as (note missing convert)
> {code:sql}
> SELECT g_0.stringkey AS c_0, (g_0.stringkey + 3.0) AS c_1 FROM smalla AS g_0
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months