[JBoss JIRA] (TEIID-4218) MongoDB metadata import fails when user has insufficient permissions
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4218?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-4218:
------------------------------------
Yes, at the time no way to exclude those tables they didn't have access to.
> MongoDB metadata import fails when user has insufficient permissions
> --------------------------------------------------------------------
>
> Key: TEIID-4218
> URL: https://issues.jboss.org/browse/TEIID-4218
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 8.12
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
>
> The vdb deployment now fails with the following errror:
> 14:26:08,810 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB mongo.1 model "importVDBSrcModel" metadata failed to load. Reason:not authorized for query on bqt.system.users: com.mongodb.MongoEx
> ception: not authorized for query on bqt.system.users
> at com.mongodb.MongoException.parse(MongoException.java:82)
> at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:292)
> at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:273)
> at com.mongodb.DBCursor._check(DBCursor.java:368)
> at com.mongodb.DBCursor._hasNext(DBCursor.java:459)
> at com.mongodb.DBCursor.hasNext(DBCursor.java:484)
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:58)
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:39)
> at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:935) [teiid-api-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) [teiid-engine-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> 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]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> The user does not have access to the system tables, but there is no way to exclude those tables from the import (like with the JDBC importer).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIID-4479) Teiid Exception on multiple values criteria
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4479?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4479.
-----------------------------------
Resolution: Duplicate Issue
Resolving as duplicate of TEIID-4406
> Teiid Exception on multiple values criteria
> -------------------------------------------
>
> Key: TEIID-4479
> URL: https://issues.jboss.org/browse/TEIID-4479
> Project: Teiid
> Issue Type: Bug
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
>
> I'm using Teiid 9.0.0 with mysql
> I'm getting an exception on the query below when putting more then one value in the criteria : ("JPVPricedSecurities"."Reply_VendorID" IN (10, 2))
> if the criteria is on one value, the query executes with success;
> The case is specifically related to the query.
> {code}
> select SUM("JPVPricedSecurities"."ContractLine_Cost") as
> "JPVPricedSecurities_Contract",
> year("SRequestPerVendor"."SRequest_DateTime") as
> "DAYOFMONTHSRequestPerVendor_"
> from "DataMarketBusinessModel"."SRequestPerVendor" "SRequestPerVendor"
> LEFT JOIN "DataMarketBusinessModel"."JPVPricedSecurities" "JPVPricedSecurities" ON "SRequestPerVendor"."SRequest_AssetID" = "JPVPricedSecurities"."Reply_AssetID"
> LEFT JOIN "datamarketModel_MM"."datamarket"."Vendor" "Vendor" ON "JPVPricedSecurities"."Reply_VendorID" = "Vendor"."VendorID"
> where ("JPVPricedSecurities"."Reply_VendorID" IN (10, 2) )
> AND ("Vendor"."Vendor" IS NOT null )
> group by
> year("SRequestPerVendor"."SRequest_DateTime")
> {code}
> Here is the exception stack:
> {code}
> Daemon Thread [http-bio-8080-exec-2] (Suspended (exception NullPointerException))
> owns: Object (id=23929)
> owns: SocketWrapper<E> (id=23848)
> LanguageBridgeFactory.translate(DependentSetCriteria) line: 426
> LanguageBridgeFactory.translate(Criteria) line: 418
> LanguageBridgeFactory.translate(CompoundCriteria) line: 494
> LanguageBridgeFactory.translate(Criteria) line: 402
> LanguageBridgeFactory.translate(Query) line: 281
> LanguageBridgeFactory.translate(QueryCommand) line: 226
> LanguageBridgeFactory.translate(SubqueryFromClause) line: 386
> LanguageBridgeFactory.translate(FromClause) line: 344
> LanguageBridgeFactory.translate(Query) line: 276
> LanguageBridgeFactory.translate(Command) line: 184
> ConnectorWorkItem.<init>(AtomicRequestMessage, ConnectorManager) line: 175
> EmbeddedServer$ProviderAwareConnectorManagerRepository$1(ConnectorManager).registerRequest(AtomicRequestMessage) line: 203
> DataTierManagerImpl.registerRequest(CommandContext, Command, String, RegisterRequestParameter) line: 1011
> TempTableDataManager.registerRequest(CommandContext, Command, String, RegisterRequestParameter) line: 179
> DependentAccessNode(AccessNode).registerRequest(Command) line: 500
> DependentAccessNode(AccessNode).openInternal() line: 268
> DependentAccessNode(AccessNode).open() line: 171
> EnhancedSortMergeJoinStrategy(JoinStrategy).openRight() line: 105
> JoinNode.nextBatchDirect() line: 223
> JoinNode(RelationalNode).nextBatch() line: 282
> GroupingNode$ProjectingTupleSource(BatchCollector$BatchProducerTupleSource).nextTuple() line: 94
> GroupingNode.groupSortPhase() line: 490
> GroupingNode.nextBatchDirect() line: 366
> GroupingNode(RelationalNode).nextBatch() line: 282
> ProjectNode.nextBatchDirect() line: 150
> ProjectNode(RelationalNode).nextBatch() line: 282
> RelationalPlan.nextBatch() line: 145
> QueryProcessor.nextBatchDirect() line: 151
> QueryProcessor.nextBatch() line: 114
> RequestWorkItem$1(BatchCollector).collectTuples(boolean) line: 164
> RequestWorkItem$1(BatchCollector).collectTuples() line: 146
> RequestWorkItem.processMore() line: 472
> RequestWorkItem.process() line: 348
> RequestWorkItem(AbstractWorkItem).run() line: 51
> RequestWorkItem.run() line: 274
> DQPCore.executeRequest(long, RequestMessage, Long) line: 313
> DQPCore.executeRequest(long, RequestMessage) line: 245
> GeneratedMethodAccessor393.invoke(Object, Object[]) line: not available
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 606
> LocalServerConnection$1$1.call() line: 177
> FutureTask<V>.run() line: 262
> DQPWorkContext.runInContext(Runnable) line: 276
> DQPWorkContext.runInContext(Callable<V>) line: 260
> LocalServerConnection$1.invoke(Object, Method, Object[]) line: 175
> $Proxy29.executeRequest(long, RequestMessage) line: not available
> StatementImpl.execute(RequestMessage, boolean) line: 673
> StatementImpl.executeSql(String[], boolean, ResultsMode, boolean, RequestOptions, boolean) line: 539
> StatementImpl.execute(String, int) line: 1060
> StatementImpl.execute(String) line: 323
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIID-4431) ASSERTION FAILED: expected reference to be not null
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4431?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4431:
---------------------------------------
Sorry there was no follow up on this. The first thing to do is to replicate the issue in 9.1+ as 8.12 is well out of support. More than likely this was already addressed by issues such as TEIID-4325
We would also need the server log of the exception as that contains the relevant stack.
> ASSERTION FAILED: expected reference to be not null
> ---------------------------------------------------
>
> Key: TEIID-4431
> URL: https://issues.jboss.org/browse/TEIID-4431
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.x
> Reporter: Chenna Krishna
> Assignee: Steven Hawkins
>
> We are using TEIID 8.12 driver for Jasper. Getting the below query when tried to trigger the query.
> Caused by: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null
> select "DOX_JB_EAM_FOLDER_SP"."EAM_CODE" as "DOX_JB_EAM_FOLDER_SP_EAM_CODE",
> "DOX_JB_EAM_FOLDER_SP"."OBJECT_NAME" as "DOX_JB_EAM_FOLDER_SP_OBJECT_NAME",
> "DT_DOX_JB_EAM_DOC_SP_CA"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_CA_R_CREATION_DATE",
> "DT_DOX_JB_EAM_DOC_SP_EAM"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_EAM_R_CREATION_DATE",
> "DT_ODS_AGENT_PROFILES"."AGENT_CODE" as "DT_ODS_AGENT_PROFILES_AGENT_CODE",
> "DT_ODS_AGENT_PROFILES"."AGENT_NAME" as "DT_ODS_AGENT_PROFILES_AGENT_NAME",
> "DT_ODS_AGENT_PROFILES"."MODIFICATION_DATE" as "DT_ODS_AGENT_PROFILES_MODIFICATION_DATE",
> "DT_ODS_AGENT_PROFILES"."OPEN_DATE" as "DT_ODS_AGENT_PROFILES_OPEN_DATE",
> "DT_ODS_AGENT_PROFILES"."STATUS" as "DT_ODS_AGENT_PROFILES_STATUS"
> from "DOX_JASPER_DXTR_USER"."JB_EAM_FOLDER_SP_SG" "DOX_JB_EAM_FOLDER_SP"
> left outer join (SELECT AGENT_CODE, AGENT_NAME, MODIFICATION_DATE, OPEN_DATE, CASE WHEN STATUS = 'A' THEN 'Inactive' WHEN STATUS = '' THEN 'Active' ELSE STATUS END AS STATUS FROM ODS.AGENT_PROFILES WHERE FLG_ACTIVE = 'Y') "DT_ODS_AGENT_PROFILES" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_ODS_AGENT_PROFILES"."AGENT_CODE")
> left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E115' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_CA" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_CA"."EAM_CODE")
> left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E109' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_EAM" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_EAM"."EAM_CODE")
> order by "DT_ODS_AGENT_PROFILES_AGENT_CODE"
> limit 200001
> Error Log:
> Caused by: com.jaspersoft.commons.dataset.DataSetException: Exception calling JRDataSource.next() for query select "DOX_JB_EAM_FOLDER_SP"."EAM_CODE" as "DOX_JB_EAM_FOLDER_SP_EAM_CODE",
> "DOX_JB_EAM_FOLDER_SP"."OBJECT_NAME" as "DOX_JB_EAM_FOLDER_SP_OBJECT_NAME",
> "DT_DOX_JB_EAM_DOC_SP_CA"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_CA_R_CREATION_DATE",
> "DT_DOX_JB_EAM_DOC_SP_EAM"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_EAM_R_CREATION_DATE",
> "DT_ODS_AGENT_PROFILES"."AGENT_CODE" as "DT_ODS_AGENT_PROFILES_AGENT_CODE",
> "DT_ODS_AGENT_PROFILES"."AGENT_NAME" as "DT_ODS_AGENT_PROFILES_AGENT_NAME",
> "DT_ODS_AGENT_PROFILES"."MODIFICATION_DATE" as "DT_ODS_AGENT_PROFILES_MODIFICATION_DATE",
> "DT_ODS_AGENT_PROFILES"."OPEN_DATE" as "DT_ODS_AGENT_PROFILES_OPEN_DATE",
> "DT_ODS_AGENT_PROFILES"."STATUS" as "DT_ODS_AGENT_PROFILES_STATUS"
> from "DOX_JASPER_DXTR_USER"."JB_EAM_FOLDER_SP_SG" "DOX_JB_EAM_FOLDER_SP"
> left outer join (SELECT AGENT_CODE, AGENT_NAME, MODIFICATION_DATE, OPEN_DATE, CASE WHEN STATUS = 'A' THEN 'Inactive' WHEN STATUS = '' THEN 'Active' ELSE STATUS END AS STATUS FROM ODS.AGENT_PROFILES WHERE FLG_ACTIVE = 'Y') "DT_ODS_AGENT_PROFILES" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_ODS_AGENT_PROFILES"."AGENT_CODE")
> left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E115' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_CA" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_CA"."EAM_CODE")
> left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E109' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_EAM" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_EAM"."EAM_CODE")
> order by "DT_ODS_AGENT_PROFILES_AGENT_CODE"
> limit 200001
> at com.jaspersoft.commons.semantic.dsimpl.JRQueryDataSet$JRDataSetIterator.next(JRQueryDataSet.java:456)
> at com.jaspersoft.commons.datarator.CachedData.fetchData(CachedData.java:217)
> ... 138 more
> Caused by: net.sf.jasperreports.engine.JRException: Error executing SQL statement for: null.
> at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:344)
> at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuter.createDatasource(JRTimezoneJdbcQueryExecuter.java:169)
> at com.jaspersoft.commons.util.JSControlledJdbcQueryExecuter.run(JSControlledJdbcQueryExecuter.java:157)
> ... 1 more
> Caused by: org.teiid.jdbc.TeiidSQLException: ASSERTION FAILED: expected reference to be not null
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:703)
> at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:64)
> at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:542)
> at org.teiid.client.util.ResultsFuture.addCompletionListener(ResultsFuture.java:148)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:538)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:260)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:73)
> at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:310)
> ... 3 more
> Regards,
> Chenna
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIID-4218) MongoDB metadata import fails when user has insufficient permissions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4218?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4218:
---------------------------------------
[~van.halbert] is the request here to support table include/exclude capabilities for mongdb import?
> MongoDB metadata import fails when user has insufficient permissions
> --------------------------------------------------------------------
>
> Key: TEIID-4218
> URL: https://issues.jboss.org/browse/TEIID-4218
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 8.12
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
>
> The vdb deployment now fails with the following errror:
> 14:26:08,810 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB mongo.1 model "importVDBSrcModel" metadata failed to load. Reason:not authorized for query on bqt.system.users: com.mongodb.MongoEx
> ception: not authorized for query on bqt.system.users
> at com.mongodb.MongoException.parse(MongoException.java:82)
> at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:292)
> at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:273)
> at com.mongodb.DBCursor._check(DBCursor.java:368)
> at com.mongodb.DBCursor._hasNext(DBCursor.java:459)
> at com.mongodb.DBCursor.hasNext(DBCursor.java:484)
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:58)
> at org.teiid.translator.mongodb.MongoDBMetadataProcessor.process(MongoDBMetadataProcessor.java:39)
> at org.teiid.translator.ExecutionFactory.getMetadata(ExecutionFactory.java:935) [teiid-api-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:73) [teiid-engine-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.1.6_2-redhat-5.jar:8.7.1.6_2-redhat-5]
> 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]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> The user does not have access to the system tables, but there is no way to exclude those tables from the import (like with the JDBC importer).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIID-4792) Unable to use WHERE clause against a JDG data source - ISPN000402: The type com.redhat.demo.sko.pojo.Call has no property named .....
by Cojan van Ballegooijen (JIRA)
Cojan van Ballegooijen created TEIID-4792:
---------------------------------------------
Summary: Unable to use WHERE clause against a JDG data source - ISPN000402: The type com.redhat.demo.sko.pojo.Call has no property named .....
Key: TEIID-4792
URL: https://issues.jboss.org/browse/TEIID-4792
Project: Teiid
Issue Type: Bug
Environment: Mac OS
JDV 6.3.4
JDG 6.6.1
JBDS 10.3.0 with JBDSIS 10.0.2
Reporter: Cojan van Ballegooijen
Assignee: Steven Hawkins
Attachments: Call_JDG_Module.zip, ChurnPrediction-vdb.xml, Contract_JDG_Module.zip, Screen Shot 2017-03-01 at 16.32.19.png, module pojo.xml, module.xml
SELECT * FROM Calls."Call" works as expected and returns all rows
Adding a where clause
SELECT * FROM Calls."Call" WHERE Calls."Call".Intlcalls > 0
generate the following error:
org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: org.hibernate.hql.ParsingException: ISPN000402: The type com.redhat.demo.sko.pojo.Call has no property named 'Intlmins'.
Elapsed Time: 0 hr, 0 min, 0 sec, 191 ms.
If I join two VBL together and run the join query it returns the same error.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIID-4356) Add asort of connection test for "connection definitions" of resource adapters
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4356?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-4356:
-------------------------------------
Fix Version/s: 10.0
Assignee: (was: Steven Hawkins)
> Add asort of connection test for "connection definitions" of resource adapters
> ------------------------------------------------------------------------------
>
> Key: TEIID-4356
> URL: https://issues.jboss.org/browse/TEIID-4356
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Marco Ardito
> Priority: Minor
> Fix For: 10.0
>
>
> Could a sort of "connection test" be implemented to verify if a "connection definition" specified for a resource adapter (eg: file, google, etc) is working, and can "connect" to the resource it's supposedly pointing to?
> Data sources(jdbc) already have this kind of test, and it is quite useful to test if there's any error in their connection definition.
> With resource adapters, one must define connection definitions, but it is not possible to test them, independently from later requests/queries (eg: reading data from .csv or .xls files, or oauth web services): one has to build all the chain and really try to get data from the source, using the vdb, hoping everything is correctly defined...
> Recently I am struggling with a custom rest oauth2 RA, and I need to define
> - security domain (with client id/secret, tokens, auth uri)
> - RA using that domain
> - a connection definition for the RA accessing the remote data source
> - a VDB using the connection definition
> - a client using the VDB to try get data in sql form
> any step could be wrong, but only the last allows to check if the whole chain is working, or not.
> For any error or failure, regular users (like me) can't do anything else than double check everything... a "test connection" button, for the connection definition, would do wonders to simplify setup debug...
> Marco
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIID-4127) Command DB Logging - SQLCMD attribute VARCHAR(8196) is too small for large queries
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4127?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4127.
-----------------------------------
Resolution: Won't Fix
Resolving as won't fix on the community side as well now that we are no longer promoting database logging. This is a simple change though for the source if it is ever needed.
> Command DB Logging - SQLCMD attribute VARCHAR(8196) is too small for large queries
> ------------------------------------------------------------------------------------
>
> Key: TEIID-4127
> URL: https://issues.jboss.org/browse/TEIID-4127
> Project: Teiid
> Issue Type: Bug
> Components: Tools
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> Command DB Logging - SQLCMD attribute VARCHAR(8196) is too small for large queries
> Setup DV to use the command logging database instead of log files.
> Was testing a large join with a left outer join to test another issue and run into
> an issue with
> Version-Release number of selected component (if applicable):
> 6.4.3
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (TEIID-4308) runtime build unit test dump lots of log and error trace
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4308?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4308.
-----------------------------------
Fix Version/s: 9.3
(was: Open To Community)
Assignee: Steven Hawkins
Resolution: Done
Took another look at this and added more logic for a graceful shutdown and unnecessary logs.
> runtime build unit test dump lots of log and error trace
> --------------------------------------------------------
>
> Key: TEIID-4308
> URL: https://issues.jboss.org/browse/TEIID-4308
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 9.1
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Priority: Optional
> Fix For: 9.3
>
>
> runtime build unit test dump lots of log and error trace, it looks
> {code}
> Jun 29, 2016 7:52:15 PM org.teiid.runtime.JBossLogger log
> INFO: START USER COMMAND:...
> org.infinispan.IllegalLifecycleStateException: ISPN000323: Cache 'preparedplan' is in 'TERMINATED' state and so it does not accept new invocations. Either restart it or recreate the cache container.
> at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:94)
> at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:76)
> at org.infinispan.commands.AbstractVisitor.visitGetKeyValueCommand(AbstractVisitor.java:85)
> at org.infinispan.commands.read.GetKeyValueCommand.acceptVisitor(GetKeyValueCommand.java:40)
> at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:336)
> at org.infinispan.cache.impl.CacheImpl.get(CacheImpl.java:411)
> at org.infinispan.cache.impl.DecoratedCache.get(DecoratedCache.java:443)
> at org.teiid.cache.infinispan.InfinispanCache.get(InfinispanCache.java:61)
> at org.teiid.dqp.internal.process.SessionAwareCache.get(SessionAwareCache.java:100)
> {code}
> In previous 8.x, i remembered no this kinds of log.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months