[JBoss JIRA] (TEIID-3877) Sort result set before BQT comparison
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3877?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-3877:
-------------------------------------
Assignee: Van Halbert (was: Steven Hawkins)
> Sort result set before BQT comparison
> -------------------------------------
>
> Key: TEIID-3877
> URL: https://issues.jboss.org/browse/TEIID-3877
> Project: Teiid
> Issue Type: Feature Request
> Components: Tools
> Environment: BQT 2.2.0
> JBoss DV 6.2
> Reporter: Jean-Pierre Matsumoto
> Assignee: Van Halbert
> Priority: Minor
>
> Currently it is not possible to ask to BQT to sort result set before it compares to reference. When an SQL query returns rows in a random order, the BQT test fails because of the different order of rows.
> I know I could use ORDER BY in the SQL but I don't like much this solution because it impacts the query plan.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (TEIID-3725) In the JDG translators, enable named cache swapping so that materialization can be supported
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3725:
------------------------------------
The native queries are currently looking like:
Before native query format: truncate cache {stageCacheName} {aliasCacheName}
After native query format: swap cache names {primaryCacheName} {stageCacheName} {aliasCacheName}
where:
primaryCacheName - is the cache that could already be available
stageCacheName - is the second cache to be used in materialization
aliasCacheName - is the cache to persist the cache alias names key<String> --> value<String>
> In the JDG translators, enable named cache swapping so that materialization can be supported
> --------------------------------------------------------------------------------------------
>
> Key: TEIID-3725
> URL: https://issues.jboss.org/browse/TEIID-3725
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.12
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> The JDG translators, that in order to support materialization, will need to enable the named cache that's referenced by the connection, to be swapped. This is due to JDG doesn't currently support renaming a cache (i.e., like table rename in JDBC). And because of that, it limits how the cache can be refreshed (don't want to clear it before re-loading).
> Ideas are:
> 1. configure translator with the 2 cache names to use (a) initial cache to read from and (b) the staging cache to use
> perform materialize load
> call SYSADMIN.setProperty to trigger the swapping of the cache names
> 2 ???
> Note: because there's no persistence in Teiid so that any cache name changes will outlive a server restart, when a restart occurs, the translator will read from the cache identified as the initial cache to read from.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (TEIID-3877) Sort result set before BQT comparison
by Jean-Pierre Matsumoto (JIRA)
Jean-Pierre Matsumoto created TEIID-3877:
--------------------------------------------
Summary: Sort result set before BQT comparison
Key: TEIID-3877
URL: https://issues.jboss.org/browse/TEIID-3877
Project: Teiid
Issue Type: Feature Request
Components: Tools
Environment: BQT 2.2.0
JBoss DV 6.2
Reporter: Jean-Pierre Matsumoto
Assignee: Steven Hawkins
Priority: Minor
Currently it is not possible to ask to BQT to sort result set before it compares to reference. When an SQL query returns rows in a random order, the BQT test fails because of the different order of rows.
I know I could use ORDER BY in the SQL but I don't like much this solution because it impacts the query plan.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (TEIID-3684) RoleBasedCredentialMapIdentityLoginModule throws exception at startup time
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3684?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3684:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1260621|https://bugzilla.redhat.com/show_bug.cgi?id=1260621] from NEW to CLOSED
> RoleBasedCredentialMapIdentityLoginModule throws exception at startup time
> --------------------------------------------------------------------------
>
> Key: TEIID-3684
> URL: https://issues.jboss.org/browse/TEIID-3684
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
>
> If a data source is configured to use RoleBasedCredentialMapIdentityLoginModule, then exception is thrown at startup \[1\], because default username and password are null. Please, add module options "username" and "password" to set up default user (similar functionality have e.g. CallerIdentityLoginModule and PassthroughIdentityLoginModule), so DV is able to properly load data source at startup when no user is authenticated and therefore no mapping could be performed.
> Example configuration \[2\]. Note, there is no exception if UsersRoles login module is used instead of RealDirect. However, it means that EAP users are separate from DV users.
> *FYI:*
> - credentialMap module option should be defined as URL (file://...). It would be nice to have this information in the documentation.
> - I tried to use unauthenticatedIdentity module option for RealmDirect, but same exception has been thrown with different root cause (realm 'ApplicationRealm' not found). I do not know why.
> \[1\]
> ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-5) Exception during createSubject()PBOX000016: Access denied: authentication failed: java.lang.SecurityException: PBOX000016: Access denied: authentication failed
> at org.jboss.security.plugins.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:84)
> at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1084)
> at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1079)
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_40]
> at org.jboss.jca.deployers.common.AbstractDsDeployer.createSubject(AbstractDsDeployer.java:1078)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:600)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:282)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:316)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:120)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]
> \[2\]
> {code:xml}
> <security-domain name="my-sec">
> <authentication>
> <login-module code="RealmDirect" flag="required">
> <module-option name="password-stacking" value="tryFirstPass"/>
> <!--<module-option name="unauthenticatedIdentity" value="guest"/>-->
> </login-module>
> <login-module code="org.teiid.jboss.RoleBasedCredentialMapIdentityLoginModule" module="org.jboss.teiid" flag="required">
> <module-option name="password-stacking" value="useFirstPass"/>
> <module-option name="credentialMap" value="file://${jboss.server.config.dir}/teiid-credentialmap.properties"/>
> </login-module>
> </authentication>
> </security-domain>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (TEIID-3872) Oracle Sequence error: Cannot infer EdmType for java type: oracle.sql.ROWID
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3872?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3872:
---------------------------------------
Yes, I have those changes ready along with TEIID-3876. I still need to work on how we are projecting out the value though rather than directly returning it from the translator layer.
> Oracle Sequence error: Cannot infer EdmType for java type: oracle.sql.ROWID
> ---------------------------------------------------------------------------
>
> Key: TEIID-3872
> URL: https://issues.jboss.org/browse/TEIID-3872
> Project: Teiid
> Issue Type: Bug
> Environment: MacOS X El Capitan, Teiid 8.12.2, Jbossdev studio, Oracle 11g
> Reporter: Ivan Lucas Vargas
> Assignee: Steven Hawkins
>
> Forum thread: https://developer.jboss.org/message/947527
> When trying to insert a record thru odata2 request when the ID field is mapped as an Oracle Sequence as described in the documentation as *<element name>:SEQUENCE=<sequence name>.<sequence value> *(https://docs.jboss.org/author/display/teiid812final/Oracle+Translator), the following error occurs:
> TEIID16013 Error occurred producing OData result.: java.lang.IllegalArgumentException: Cannot infer EdmType for java type: oracle.sql.ROWID
> at org.odata4j.core.OProperties.simple(OProperties.java:40) [odata-core-0.8.10.jar:0.8.10]
> at org.teiid.odata.ODataSQLBuilder.buildEntityKey(ODataSQLBuilder.java:678) [classes:]
> at org.teiid.odata.TeiidProducer.createEntity(TeiidProducer.java:232) [classes:]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:129) [odata-core-0.8.10.jar:0.8.10]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:116) [odata-core-0.8.10.jar:0.8.10]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_45]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_45]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_45]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_45]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:541) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:523) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:125) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:118) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:65) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.0.Final-redhat-15.jar:7.5.0.Final-redhat-15]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45]
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (TEIID-3872) Oracle Sequence error: Cannot infer EdmType for java type: oracle.sql.ROWID
by Ivan Lucas Vargas (JIRA)
[ https://issues.jboss.org/browse/TEIID-3872?page=com.atlassian.jira.plugin... ]
Ivan Lucas Vargas commented on TEIID-3872:
------------------------------------------
Yes, exactly. I need to get the ID generated from the insert command.
The Oracle JDBC Driver 3.0+ says that If I pass, along with the insert command in the prepared statement, the column name of my primary key, I can get it's value by getGeneratedKeys(). If I don't pass the column name, the ROWID is returned.
> Oracle Sequence error: Cannot infer EdmType for java type: oracle.sql.ROWID
> ---------------------------------------------------------------------------
>
> Key: TEIID-3872
> URL: https://issues.jboss.org/browse/TEIID-3872
> Project: Teiid
> Issue Type: Bug
> Environment: MacOS X El Capitan, Teiid 8.12.2, Jbossdev studio, Oracle 11g
> Reporter: Ivan Lucas Vargas
> Assignee: Steven Hawkins
>
> Forum thread: https://developer.jboss.org/message/947527
> When trying to insert a record thru odata2 request when the ID field is mapped as an Oracle Sequence as described in the documentation as *<element name>:SEQUENCE=<sequence name>.<sequence value> *(https://docs.jboss.org/author/display/teiid812final/Oracle+Translator), the following error occurs:
> TEIID16013 Error occurred producing OData result.: java.lang.IllegalArgumentException: Cannot infer EdmType for java type: oracle.sql.ROWID
> at org.odata4j.core.OProperties.simple(OProperties.java:40) [odata-core-0.8.10.jar:0.8.10]
> at org.teiid.odata.ODataSQLBuilder.buildEntityKey(ODataSQLBuilder.java:678) [classes:]
> at org.teiid.odata.TeiidProducer.createEntity(TeiidProducer.java:232) [classes:]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:129) [odata-core-0.8.10.jar:0.8.10]
> at org.odata4j.producer.resources.EntitiesRequestResource.createEntity(EntitiesRequestResource.java:116) [odata-core-0.8.10.jar:0.8.10]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_45]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_45]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_45]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_45]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:541) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:523) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:125) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:118) [classes:]
> at org.teiid.odata.ODataServlet.service(ODataServlet.java:65) [classes:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.9.Final-redhat-7.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.0.Final-redhat-15.jar:7.5.0.Final-redhat-15]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.3.Final.jar:7.5.3.Final]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45]
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (TEIID-3876) Add an option to import RowId as binary
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3876:
-------------------------------------
Summary: Add an option to import RowId as binary
Key: TEIID-3876
URL: https://issues.jboss.org/browse/TEIID-3876
Project: Teiid
Issue Type: Enhancement
Components: JDBC Connector, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.13, 8.12.4
RowId values will be seen as object type, which may not be useful for consumers. We should offer a mapping to varbinary to pull the raw byte value, which can be properly typed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (TEIID-3875) Many info messages upon startup that start with: TEIID31173 Inherent
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3875?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3875:
---------------------------------------
> So the user expectation here is that the view can't be used for simple INSERT/UPDATE/DELETE, and that a trigger must be defined to specifically map the tables/columns.
Yes. It needs corrected since the message is out of order. It should be:
Inherent UPDATE against VDB_Lineage.Model_Tables has the following issues: Multiple failures occurred during validation:The updatable view query has a FROM clause that is not a single table, pass-through processing will not be used for UPDATE/DELETE operations., The updatable view has no valid target for UPDATEs.
The issue here is that there can be quite a bit that prevents these updates from occurring that is not stored/returned by later exceptions should an update be attempted. So rather than having this information not reported, we're logging it once during VDB startup. This is basically a soft metadata error - a view has been marked as updatable, but really isn't. The other option would be to log at a detail level.
> Many info messages upon startup that start with: TEIID31173 Inherent
> ---------------------------------------------------------------------
>
> Key: TEIID-3875
> URL: https://issues.jboss.org/browse/TEIID-3875
> Project: Teiid
> Issue Type: Quality Risk
> Components: Server
> Affects Versions: 8.12.2
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Attachments: server.log
>
>
> See that attached server log that shows a page full of the following similar message:
> [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 1) TEIID31173 Inherent Multiple failures occurred ..
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months