[JBoss JIRA] (TEIID-4945) Teiid java client error (Column name "VDBName" does not exist)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4945?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4945.
-----------------------------------
Resolution: Rejected
Marking as rejected as it looks like the client code is expecting JDBC 3 column name behavior.
> Teiid java client error (Column name "VDBName" does not exist)
> --------------------------------------------------------------
>
> Key: TEIID-4945
> URL: https://issues.jboss.org/browse/TEIID-4945
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 9.2.3
> Environment: Running teiid 9.2.3 on wildfly, failing using java client with 9.2.3 driver and sucess using protege with driver 9.2.3. both use ontop for mapping the data from db to the ontology.
> Reporter: Fábio Guilherme
> Assignee: Steven Hawkins
> Attachments: screenshot-1.png
>
>
> This java client uses ontop to make the mapping from a db to a ontology. I had prior version where i was mapping my data from a postgres db to the ontology using ontop, in my recent version i changed the db to a teiid db(where i get the error).
> Using teiid 9.2.3 and wildfly with java client with 9.2.3 driver i get this error:
> {color:red}Error obtaining the Metadataorg.teiid.jdbc.TeiidSQLException: Column name "VDBName" does not exist.
> 09:31:15.411 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - Could not initialize the Quest query answering engine. Answering queries will not be available.
> 09:31:15.427 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - java.lang.NullPointerException
> it.unibz.krdb.obda.model.OBDAException: java.lang.NullPointerException{color}
> i used the same driver(9.2.3) on protege with ontop-pro and i dont get any error.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4947) Error with Salesforce translator if criteria on outer join on a custom table is from the right side table
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4947?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4947:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1459172
Bugzilla Update: Perform
> Error with Salesforce translator if criteria on outer join on a custom table is from the right side table
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIID-4947
> URL: https://issues.jboss.org/browse/TEIID-4947
> Project: Teiid
> Issue Type: Bug
> Components: Salesforce Connector
> Affects Versions: 8.7.11.6_2, 8.12.10.6_3
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> Running a left outer join between a parent and child custom table in salesforce results in an error:
> select a.id, a.name, a.LastModifiedDate, b.Order_Recipe_Steps__c, b.name
> from MPRS_Salesforce.Media_Prep_Order_Recipe_Steps__c a left outer join "MPRS_Salesforce"."Recipe_Step_Detail__c" b
> on (a.id = b.Order_Recipe_Steps__c)
> where b.LastModifiedDate >= parsetimestamp('2016-05-04 15:01:03.0', 'yyyy-MM-dd hh:mm:ss.s')
> Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 MPRS_Salesforce: com.sforce.soap.partner.InvalidSObjectFault: INVALID_TYPE:
> Recipe_Step_Detail__c.Catalog_Item__c FROM Recipe_Step_Detail__cs) FROM Media_Prep_Order_Recipe_Steps__c
> ^
> ERROR at Row:1:Column:1137
> Didn't understand relationship 'Recipe_Step_Detail__cs' in FROM part of query call. If you are attempting to use a custom relationship, be sure to append the '__r' after the custom relationship name. Please reference your WSDL or the describe call for the appropriate names.
> SQLState: 50000
> ErrorCode: 30504
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-3398) Use Weka algorithm to caculate serializing, deserializing linear regression rate
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3398?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-3398:
-------------------------------------
Assignee: Van Halbert (was: Kylin Soong)
> Use Weka algorithm to caculate serializing, deserializing linear regression rate
> --------------------------------------------------------------------------------
>
> Key: TEIID-3398
> URL: https://issues.jboss.org/browse/TEIID-3398
> Project: Teiid
> Issue Type: Feature Request
> Components: Sizing Application
> Reporter: Kylin Soong
> Assignee: Van Halbert
> Priority: Optional
>
> We have lots of data points {(size i, time i), i = 1, ..., n}, the goal is to find the equation of the straight line like
> time = K * size
> The key is to find the linear regression rate K, current we do not use any algorithm, Weka(http://sourceforge.net/projects/weka/) have algorithm to fine the K, we may use the Weka to enhance Sizing application
> Doc link: http://www.cs.waikato.ac.nz/~ml/weka/documentation.html
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4489) Adjust defaults and use of 1 to 10 data sources to recommend the SMALL size
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4489?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-4489:
-------------------------------------
Assignee: Van Halbert (was: Kylin Soong)
> Adjust defaults and use of 1 to 10 data sources to recommend the SMALL size
> ---------------------------------------------------------------------------
>
> Key: TEIID-4489
> URL: https://issues.jboss.org/browse/TEIID-4489
> Project: Teiid
> Issue Type: Enhancement
> Components: Sizing Application
> Affects Versions: 9.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 10.x
>
>
> Based on recommendations:
> small : 16 cores, with at least 32 GB RAM. 2 DV instances. (small means may be 5 ~10 sources, rows into millions, YMMV)
> medium : 32 cores with 64 GB RAM, 4 DV instances. (medium means may be 10 ~ 20 sources, rows into multi-millions, YMMV)
> Large: custom
> The defaults in the sizing applications, along with selecting 1 to 10 data sources, should result in the SMALL recommendation. It should be clear to indicate the number of instances and the size recommendation per instance.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-3683) Enhance the formula for caculating core size
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3683?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-3683:
-------------------------------------
Assignee: Van Halbert (was: Kylin Soong)
> Enhance the formula for caculating core size
> --------------------------------------------
>
> Key: TEIID-3683
> URL: https://issues.jboss.org/browse/TEIID-3683
> Project: Teiid
> Issue Type: Enhancement
> Components: Sizing Application
> Reporter: Kylin Soong
> Assignee: Van Halbert
> Priority: Minor
> Fix For: 9.3.1
>
> Attachments: sizing-tools-cores.png
>
>
> I think we can consider to enhance in the following aspects:
> 1. Q7 is hard for user to input
> Q7 need some pre-test or run sample query via POC, this not easy for user to input, also they may feels confused.
> 2. How to caculate core size?
> Current we consider through serialize/deserialize, the linear serialize/deserialize percentage get from trial in my local pc, this may need more test/review.
> 3. Whether we can use runnable app replace Web UI
> If use runnable app like AdminShell, most of questions in attached png can cacualate and get a precise input,
> Any idea/advice for this?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4945) Teiid java client error (Column name "VDBName" does not exist)
by Fábio Guilherme (JIRA)
[ https://issues.jboss.org/browse/TEIID-4945?page=com.atlassian.jira.plugin... ]
Fábio Guilherme commented on TEIID-4945:
----------------------------------------
thank you, it worked perfectly, i just changed the "?" with a ";".
> Teiid java client error (Column name "VDBName" does not exist)
> --------------------------------------------------------------
>
> Key: TEIID-4945
> URL: https://issues.jboss.org/browse/TEIID-4945
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 9.2.3
> Environment: Running teiid 9.2.3 on wildfly, failing using java client with 9.2.3 driver and sucess using protege with driver 9.2.3. both use ontop for mapping the data from db to the ontology.
> Reporter: Fábio Guilherme
> Assignee: Steven Hawkins
> Attachments: screenshot-1.png
>
>
> This java client uses ontop to make the mapping from a db to a ontology. I had prior version where i was mapping my data from a postgres db to the ontology using ontop, in my recent version i changed the db to a teiid db(where i get the error).
> Using teiid 9.2.3 and wildfly with java client with 9.2.3 driver i get this error:
> {color:red}Error obtaining the Metadataorg.teiid.jdbc.TeiidSQLException: Column name "VDBName" does not exist.
> 09:31:15.411 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - Could not initialize the Quest query answering engine. Answering queries will not be available.
> 09:31:15.427 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - java.lang.NullPointerException
> it.unibz.krdb.obda.model.OBDAException: java.lang.NullPointerException{color}
> i used the same driver(9.2.3) on protege with ontop-pro and i dont get any error.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4945) Teiid java client error (Column name "VDBName" does not exist)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4945?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4945:
---------------------------------------
Sorry, I put in the wrong delimiter - jdbc:teiid:ontop_dbVDB@mm://localhost:31000;useJDBC4ColumnNameAndLabelSemantics=false
Properties are documented in the client guide - https://teiid.gitbooks.io/documents/content/client-dev/Driver_Connection....
> Teiid java client error (Column name "VDBName" does not exist)
> --------------------------------------------------------------
>
> Key: TEIID-4945
> URL: https://issues.jboss.org/browse/TEIID-4945
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 9.2.3
> Environment: Running teiid 9.2.3 on wildfly, failing using java client with 9.2.3 driver and sucess using protege with driver 9.2.3. both use ontop for mapping the data from db to the ontology.
> Reporter: Fábio Guilherme
> Assignee: Steven Hawkins
> Attachments: screenshot-1.png
>
>
> This java client uses ontop to make the mapping from a db to a ontology. I had prior version where i was mapping my data from a postgres db to the ontology using ontop, in my recent version i changed the db to a teiid db(where i get the error).
> Using teiid 9.2.3 and wildfly with java client with 9.2.3 driver i get this error:
> {color:red}Error obtaining the Metadataorg.teiid.jdbc.TeiidSQLException: Column name "VDBName" does not exist.
> 09:31:15.411 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - Could not initialize the Quest query answering engine. Answering queries will not be available.
> 09:31:15.427 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - java.lang.NullPointerException
> it.unibz.krdb.obda.model.OBDAException: java.lang.NullPointerException{color}
> i used the same driver(9.2.3) on protege with ontop-pro and i dont get any error.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4945) Teiid java client error (Column name "VDBName" does not exist)
by Fábio Guilherme (JIRA)
[ https://issues.jboss.org/browse/TEIID-4945?page=com.atlassian.jira.plugin... ]
Fábio Guilherme commented on TEIID-4945:
----------------------------------------
where can i find the list of properties?
Using the one you gave me a get this error:
!screenshot-1.png|thumbnail!
> Teiid java client error (Column name "VDBName" does not exist)
> --------------------------------------------------------------
>
> Key: TEIID-4945
> URL: https://issues.jboss.org/browse/TEIID-4945
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 9.2.3
> Environment: Running teiid 9.2.3 on wildfly, failing using java client with 9.2.3 driver and sucess using protege with driver 9.2.3. both use ontop for mapping the data from db to the ontology.
> Reporter: Fábio Guilherme
> Assignee: Steven Hawkins
> Attachments: screenshot-1.png
>
>
> This java client uses ontop to make the mapping from a db to a ontology. I had prior version where i was mapping my data from a postgres db to the ontology using ontop, in my recent version i changed the db to a teiid db(where i get the error).
> Using teiid 9.2.3 and wildfly with java client with 9.2.3 driver i get this error:
> {color:red}Error obtaining the Metadataorg.teiid.jdbc.TeiidSQLException: Column name "VDBName" does not exist.
> 09:31:15.411 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - Could not initialize the Quest query answering engine. Answering queries will not be available.
> 09:31:15.427 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - java.lang.NullPointerException
> it.unibz.krdb.obda.model.OBDAException: java.lang.NullPointerException{color}
> i used the same driver(9.2.3) on protege with ontop-pro and i dont get any error.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4945) Teiid java client error (Column name "VDBName" does not exist)
by Fábio Guilherme (JIRA)
[ https://issues.jboss.org/browse/TEIID-4945?page=com.atlassian.jira.plugin... ]
Fábio Guilherme updated TEIID-4945:
-----------------------------------
Attachment: screenshot-1.png
> Teiid java client error (Column name "VDBName" does not exist)
> --------------------------------------------------------------
>
> Key: TEIID-4945
> URL: https://issues.jboss.org/browse/TEIID-4945
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 9.2.3
> Environment: Running teiid 9.2.3 on wildfly, failing using java client with 9.2.3 driver and sucess using protege with driver 9.2.3. both use ontop for mapping the data from db to the ontology.
> Reporter: Fábio Guilherme
> Assignee: Steven Hawkins
> Attachments: screenshot-1.png
>
>
> This java client uses ontop to make the mapping from a db to a ontology. I had prior version where i was mapping my data from a postgres db to the ontology using ontop, in my recent version i changed the db to a teiid db(where i get the error).
> Using teiid 9.2.3 and wildfly with java client with 9.2.3 driver i get this error:
> {color:red}Error obtaining the Metadataorg.teiid.jdbc.TeiidSQLException: Column name "VDBName" does not exist.
> 09:31:15.411 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - Could not initialize the Quest query answering engine. Answering queries will not be available.
> 09:31:15.427 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - java.lang.NullPointerException
> it.unibz.krdb.obda.model.OBDAException: java.lang.NullPointerException{color}
> i used the same driver(9.2.3) on protege with ontop-pro and i dont get any error.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (TEIID-4948) java.lang.IllegalArgumentException: No marshaller registered for ispn.G1
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4948?page=com.atlassian.jira.plugin... ]
Van Halbert reassigned TEIID-4948:
----------------------------------
Assignee: Van Halbert (was: Ramesh Reddy)
> java.lang.IllegalArgumentException: No marshaller registered for ispn.G1
> ------------------------------------------------------------------------
>
> Key: TEIID-4948
> URL: https://issues.jboss.org/browse/TEIID-4948
> Project: Teiid
> Issue Type: Bug
> Components: Infinispan
> Affects Versions: 9.3
> Reporter: Van Halbert
> Assignee: Van Halbert
> Attachments: jdg-remote-cache-ddl-vdb.xml
>
>
> Deploying a VDB that contains 2 models with tables that reference the same JNDI, but defined different caches. (see vdb attached).
> Can query both caches and based on results, I know they are not the same cache.
> When performing an insert to the first table (G1) it works. When performing an insert to other table (G2), get the IllegalArgmentException.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years