[JBoss JIRA] (TEIID-3658) VDBs may start before transport service
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3658:
-------------------------------------
Ok, that is how I originally had it, I thought you wanted to keep the current behavior in case.
> VDBs may start before transport service
> ---------------------------------------
>
> Key: TEIID-3658
> URL: https://issues.jboss.org/browse/TEIID-3658
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Critical
> Labels: Beta2
> Fix For: 8.12
>
>
> VDBs may start before transport services, which is an issue for ODBC access as the enabled flag on the vdbrepository is toggled in by the transport. Any vdbs loaded prior to that point will not be properly accessible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3658) VDBs may start before transport service
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3658:
---------------------------------------
Those changes won't quite work. There can be no toggling of the behavior from the transport - as we can't guarantee when it will get called. The system property should be something along the lines of "add pg metadata" and default it to true. Someone who has no pg transport and doesn't want the pg metadata then will only have to toggle one system property. Otherwise there will be no action needed by anyone else.
> VDBs may start before transport service
> ---------------------------------------
>
> Key: TEIID-3658
> URL: https://issues.jboss.org/browse/TEIID-3658
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Critical
> Labels: Beta2
> Fix For: 8.12
>
>
> VDBs may start before transport services, which is an issue for ODBC access as the enabled flag on the vdbrepository is toggled in by the transport. Any vdbs loaded prior to that point will not be properly accessible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3658) VDBs may start before transport service
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3658.
---------------------------------
Resolution: Done
Labels: Beta2 (was: )
- Added a System property "org.teiid.loadPgMetadataOnPgTransport" to keep the old behavior as is, that is to only include the pg system metadata when the pg transport is available. The default value is "false"
- Added a VDB based property "exclude-pg-metadata" to explicitly exclude pg system metadata per VDB. The default value for this property is also "false"
In absence of both properties above, the pg system metadata is always included with every VDB.
> VDBs may start before transport service
> ---------------------------------------
>
> Key: TEIID-3658
> URL: https://issues.jboss.org/browse/TEIID-3658
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Critical
> Labels: Beta2
> Fix For: 8.12
>
>
> VDBs may start before transport services, which is an issue for ODBC access as the enabled flag on the vdbrepository is toggled in by the transport. Any vdbs loaded prior to that point will not be properly accessible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3663) ST_Transform only works in tests
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3663?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3663:
---------------------------------------
This is a regression from TEIID-3380 - the security helper authenticate method does not associate a new security context, so we are not setting the subject as expected on the work context. If it were there, then the would be no further authentication calls.
> ST_Transform only works in tests
> --------------------------------
>
> Key: TEIID-3663
> URL: https://issues.jboss.org/browse/TEIID-3663
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
>
> From one of the tests; this fails against an actual server (JBoss kit).
> {code}
> select st_transform(st_geomfromtext('POINT(-118 34)',4326),3310);
> {code}
> {code}
> ERROR: TEIID30328 Unable to evaluate st_transform(?, 3310): TEIID30384 Error while evaluating function st_transform
> DETAIL: org.teiid.jdbc.TeiidSQLException: TEIID30328 Unable to evaluate st_transform(?, 3310): TEIID30384 Error while evaluating function st_transform
> {code}
> {code}
> 00:02:59,143 INFO [org.teiid.SECURITY] (Worker2_QueryProcessorQueue6) tF6aPUsmLmU/ TEIID40115 Local pass-through connection implicitly closing session tF6aPUsmLmU/ so that the connection can be used in a different security context.
> 00:02:59,144 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue6) tF6aPUsmLmU/ TEIID30020 Processing exception for request tF6aPUsmLmU/.4 'TEIID30328 Unable to evaluate st_transform(?, 3310): TEIID30384 Error while evaluating function st_transform'. Originally ExpressionEvaluationException 'Expected argument to be non-null but got null' ArgCheck.java:303.: org.teiid.api.exception.query.ExpressionEvaluationException: TEIID30328 Unable to evaluate st_transform(?, 3310): TEIID30384 Error while evaluating function st_transform
> at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:631) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.evaluate(QueryRewriter.java:2122) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.rewriteExpressionDirect(QueryRewriter.java:2112) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.access$000(QueryRewriter.java:101) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter$3.replaceExpression(QueryRewriter.java:626) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.visitor.ExpressionMappingVisitor.visit(ExpressionMappingVisitor.java:162) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.symbol.ExpressionSymbol.acceptVisitor(ExpressionSymbol.java:63) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.AbstractNavigator.visitVisitor(AbstractNavigator.java:54) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.postVisitVisitor(PreOrPostOrderNavigator.java:61) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:183) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.symbol.ExpressionSymbol.acceptVisitor(ExpressionSymbol.java:63) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:63) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:76) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:342) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.lang.Select.acceptVisitor(Select.java:168) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.PostOrderNavigator.doVisit(PostOrderNavigator.java:40) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.rewriteExpressions(QueryRewriter.java:633) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.rewriteQuery(QueryRewriter.java:471) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.rewriteCommand(QueryRewriter.java:222) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.rewrite(QueryRewriter.java:167) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.rewrite(QueryRewriter.java:171) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:413) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.Request.processRequest(Request.java:461) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:632) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:333) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:271) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
> Caused by: org.teiid.api.exception.query.FunctionExecutionException: TEIID30384 Error while evaluating function st_transform
> at org.teiid.query.function.FunctionDescriptor.invokeFunction(FunctionDescriptor.java:295) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:1320) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.eval.Evaluator.internalEvaluate(Evaluator.java:659) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:629) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> ... 32 more
> Caused by: org.teiid.api.exception.query.FunctionExecutionException: 38000 TEIID31163 Failed to lookup proj4 text.
> at org.teiid.query.function.GeometryTransformUtils.lookupProj4Text(GeometryTransformUtils.java:109) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.function.GeometryTransformUtils.transform(GeometryTransformUtils.java:78) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.function.GeometryTransformUtils.transform(GeometryTransformUtils.java:64) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.function.GeometryFunctionMethods.transform(GeometryFunctionMethods.java:253) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_79]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_79]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_79]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_79]
> at org.teiid.query.function.FunctionDescriptor.invokeFunction(FunctionDescriptor.java:281) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> ... 35 more
> Caused by: org.teiid.jdbc.TeiidSQLException: Expected argument to be non-null but got null
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:671) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:535) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:73) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.function.GeometryTransformUtils.lookupProj4Text(GeometryTransformUtils.java:103) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> ... 43 more
> Caused by: org.teiid.core.TeiidComponentException: Expected argument to be non-null but got null
> at org.teiid.client.util.ExceptionUtil.convertException(ExceptionUtil.java:65) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:186) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at com.sun.proxy.$Proxy18.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:669) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> ... 47 more
> Caused by: java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:303) [teiid-common-core-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:289) [teiid-common-core-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.services.SessionServiceImpl.createSession(SessionServiceImpl.java:150) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.transport.LogonImpl.logon(LogonImpl.java:137) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.transport.LogonImpl.logon(LogonImpl.java:121) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_79]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_79]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_79]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_79]
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:180) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_79]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:178) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at com.sun.proxy.$Proxy48.logon(Unknown Source)
> at org.teiid.transport.LocalServerConnection.authenticate(LocalServerConnection.java:142) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:174) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> ... 49 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3662) IN predicate against a materialized/temp table index without an order by returns wrong results
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3662?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3662:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1257964
Bugzilla Update: Perform
> IN predicate against a materialized/temp table index without an order by returns wrong results
> ----------------------------------------------------------------------------------------------
>
> Key: TEIID-3662
> URL: https://issues.jboss.org/browse/TEIID-3662
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.12, 8.11.3
>
>
> Seeing strange behavior when doing a simple select from {{SPATIAL_REF_SYS}}.
> This works as expected:
> {code}
> select srid, proj4text from spatial_ref_sys where srid in (3875,4326);
> srid | proj4text
> ------+----------------------------------------------------------------------------------------------------------------
> 3875 | +proj=tmerc +lat_0=0 +lon_0=21 +k=1 +x_0=21500000 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs
> 4326 | +proj=longlat +datum=WGS84 +no_defs
> (2 rows)
> {code}
> Swapping the values in the IN causes only one row to be returned.
> {code}
> select srid, proj4text from spatial_ref_sys where srid in (4326,3875);
> srid | proj4text
> ------+-------------------------------------
> 4326 | +proj=longlat +datum=WGS84 +no_defs
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3662) IN predicate against a materialized/temp table index without an order by returns wrong results
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3662?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3662.
-----------------------------------
Resolution: Done
The root cause was that the tuplebrowser expected the value set to be sorted, but it was only being sorted when an order by against the index was specified.
> IN predicate against a materialized/temp table index without an order by returns wrong results
> ----------------------------------------------------------------------------------------------
>
> Key: TEIID-3662
> URL: https://issues.jboss.org/browse/TEIID-3662
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.12, 8.11.3
>
>
> Seeing strange behavior when doing a simple select from {{SPATIAL_REF_SYS}}.
> This works as expected:
> {code}
> select srid, proj4text from spatial_ref_sys where srid in (3875,4326);
> srid | proj4text
> ------+----------------------------------------------------------------------------------------------------------------
> 3875 | +proj=tmerc +lat_0=0 +lon_0=21 +k=1 +x_0=21500000 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs
> 4326 | +proj=longlat +datum=WGS84 +no_defs
> (2 rows)
> {code}
> Swapping the values in the IN causes only one row to be returned.
> {code}
> select srid, proj4text from spatial_ref_sys where srid in (4326,3875);
> srid | proj4text
> ------+-------------------------------------
> 4326 | +proj=longlat +datum=WGS84 +no_defs
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3662) IN predicate against a materialized/temp table index without an order by returns wrong results
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3662?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3662:
----------------------------------
Summary: IN predicate against a materialized/temp table index without an order by returns wrong results (was: IN predicate against a materialized table index without an order by returns wrong results)
> IN predicate against a materialized/temp table index without an order by returns wrong results
> ----------------------------------------------------------------------------------------------
>
> Key: TEIID-3662
> URL: https://issues.jboss.org/browse/TEIID-3662
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.12, 8.11.3
>
>
> Seeing strange behavior when doing a simple select from {{SPATIAL_REF_SYS}}.
> This works as expected:
> {code}
> select srid, proj4text from spatial_ref_sys where srid in (3875,4326);
> srid | proj4text
> ------+----------------------------------------------------------------------------------------------------------------
> 3875 | +proj=tmerc +lat_0=0 +lon_0=21 +k=1 +x_0=21500000 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs
> 4326 | +proj=longlat +datum=WGS84 +no_defs
> (2 rows)
> {code}
> Swapping the values in the IN causes only one row to be returned.
> {code}
> select srid, proj4text from spatial_ref_sys where srid in (4326,3875);
> srid | proj4text
> ------+-------------------------------------
> 4326 | +proj=longlat +datum=WGS84 +no_defs
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3658) VDBs may start before transport service
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3658:
-------------------------------------
What I have added is like
{code}
vdb.addProperty("exclude-pg-metadata", "true");
{code}
The default value is set to "false". So we will add the System property to keep the old behavior.
> VDBs may start before transport service
> ---------------------------------------
>
> Key: TEIID-3658
> URL: https://issues.jboss.org/browse/TEIID-3658
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Critical
> Fix For: 8.12
>
>
> VDBs may start before transport services, which is an issue for ODBC access as the enabled flag on the vdbrepository is toggled in by the transport. Any vdbs loaded prior to that point will not be properly accessible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3656) Maven assembly plugin moduleSet includeDependencies set to true scope too large
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3656?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3656:
-------------------------------------
I believe that is the assumption we built with.
> Maven assembly plugin moduleSet includeDependencies set to true scope too large
> -------------------------------------------------------------------------------
>
> Key: TEIID-3656
> URL: https://issues.jboss.org/browse/TEIID-3656
> Project: Teiid
> Issue Type: Quality Risk
> Components: Build/Kits
> Affects Versions: 8.12
> Reporter: Kylin Soong
>
> The assembly plugin moduleSet includeDependencies configuration under "build/assembly/jboss-as7/dist.xml":
> {code}
> <moduleSet>
> <includeSubModules>true</includeSubModules>
> <useAllReactorProjects>true</useAllReactorProjects>
> <includes>
> <include>org.jboss.teiid:teiid-jboss-integration</include>
> </includes>
> <binaries>
> <includeDependencies>true</includeDependencies>
> {code}
> the scope of this setting(includeDependencies is true,) is to large, it scope to all modules.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months