[ https://jira.jboss.org/jira/browse/TEIID-104?page=com.atlassian.jira.plug... ]
Steven Hawkins resolved TEIID-104.
----------------------------------
Resolution: Done
Updated to the latest changes in 6.2. All diagrams were removed. There should probably be more material on built-in connector properties and the BasicConnector class.
> Connector development documentation out-of-date
> -----------------------------------------------
>
> Key: TEIID-104
> URL: https://jira.jboss.org/jira/browse/TEIID-104
> Project: Teiid
> Issue Type: Sub-task
> Components: Connector API, Documentation
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 6.2.0
>
>
> The included diagrams and documentation are not up-to-date with the limit, intersect, and except features. Documentation needs to be added for GlobalCapabilitiesProvider as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Expose via the adminapi a method to obtain the models
-----------------------------------------------------
Key: TEIID-823
URL: https://jira.jboss.org/jira/browse/TEIID-823
Project: Teiid
Issue Type: Sub-task
Components: AdminApi, Console, Jopr Plugin
Affects Versions: 6.3.0
Reporter: Van Halbert
Assignee: Steven Hawkins
An api method that exposes the models for a given vdb needs to be added. Yes, this information could be obtained by querying the system vdb. However, for consistency, any administration action that needs to be accomplished should be done in the same manner (i.e., via adminapi). Also, in order to make connector binding assignment to a model, must know what models exist in the vdb.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/jira/browse/TEIID-820?page=com.atlassian.jira.plug... ]
Ramesh Reddy resolved TEIID-820.
--------------------------------
Resolution: Done
Assignee: Ramesh Reddy
Added the Derby XA Connector type to the configuration.xml file. The name is "Apache Derby XA Network Connector"
> Add Derby XA Connector Type to Designer
> ---------------------------------------
>
> Key: TEIID-820
> URL: https://jira.jboss.org/jira/browse/TEIID-820
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 6.2.0
> Reporter: Ted Jones
> Assignee: Ramesh Reddy
>
> In order to support an updateable Portfolio database for our Teiid example, we need to be able to create a Derby XA connector. This connector type need to be added to the list of our pre-defined connectors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://jira.jboss.org/jira/browse/TEIID-820?page=com.atlassian.jira.plug... ]
Ramesh Reddy moved TEIIDDES-225 to TEIID-820:
---------------------------------------------
Project: Teiid (was: Teiid Designer)
Key: TEIID-820 (was: TEIIDDES-225)
Affects Version/s: 6.2.0
(was: 6.2.0)
> Add Derby XA Connector Type to Designer
> ---------------------------------------
>
> Key: TEIID-820
> URL: https://jira.jboss.org/jira/browse/TEIID-820
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 6.2.0
> Reporter: Ted Jones
>
> In order to support an updateable Portfolio database for our Teiid example, we need to be able to create a Derby XA connector. This connector type need to be added to the list of our pre-defined connectors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
java.lang.NoClassDefFoundError: org/teiid/adminapi/SystemObject when connecting to Teiid embeded
------------------------------------------------------------------------------------------------
Key: TEIID-815
URL: https://jira.jboss.org/jira/browse/TEIID-815
Project: Teiid
Issue Type: Bug
Components: Embedded
Affects Versions: 6.2.0
Environment: Teiid embedded night build of Sep 1. Connecting to vdb from SQuirrel using file path config.
Reporter: John Doyle
Assignee: Steven Hawkins
Fix For: 6.2.0
I moved a VDB I was testing in yesterday's build to today's, and now get this exception when connecting.
java.lang.NoClassDefFoundError: org/teiid/adminapi/SystemObject
I'm trying to get the stack, currently can't copy/paste from SQuirrel for some reason.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Inversion of convert(string, ...) is not always possible.
---------------------------------------------------------
Key: TEIID-744
URL: https://jira.jboss.org/jira/browse/TEIID-744
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.2.0
The parsing routines for date and numeric types from string allow for non-canonical string forms. Inverting the convert assumes that the standard toString format must be used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira