[JBoss JIRA] Commented: (TEIID-143) Query should 'find' connector types and jars rather than have them predefined in the config.
by Ramesh Reddy (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-143?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIID-143:
------------------------------------
The requirements are
1) It must be discoverable, should be able define them without modifications to other parts of system
2) Prefer to inherit common properties, so that the all connector specific properties can be defined in one place
3) Should be able to load dependent jars in non-delegating class loader
4) Should be able to define the third party dependencies externally to the artifact (CAF includes them, but should have option to specify externally, if needed)
5) Preferably single artifact (Like CAF)
The comment above in one solution, where CAF file includes the type information and all the necessary jars. But this does not satisfy (4). We could additionally support ".cdk" files in a directory along with their dependencies to support the item (4).
> Query should 'find' connector types and jars rather than have them predefined in the config.
> --------------------------------------------------------------------------------------------
>
> Key: TEIID-143
> URL: https://jira.jboss.org/jira/browse/TEIID-143
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 6.0.0
> Reporter: John Doyle
> Fix For: 6.1.0
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> Currently, dqp as delived with Designer is preconfigured with connector types. I think it should discover the connectors that are available upon startup. This would make it easier to add connectors to a kit. The current process for adding a connector to a kit is manual and error prone. We have problems with it on nearly every release.
> This is also an attractive feature for embedding query in other environments.
--
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
15 years, 9 months
[JBoss JIRA] Commented: (TEIID-309) System Host setup issues
by Ramesh Reddy (JIRA)
[ https://jira.jboss.org/jira/browse/TEIID-309?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIID-309:
------------------------------------
I added the host properties to the Host object, so they are available when asked for Host information through Admin API. However, looks like Console directly tries to feed from configuration and uses Property definitions to show them. Looks like to show them in the Console requires more work.
> System Host setup issues
> ------------------------
>
> Key: TEIID-309
> URL: https://jira.jboss.org/jira/browse/TEIID-309
> Project: Teiid
> Issue Type: Task
> Components: Build/Kits
> Affects Versions: 6.0.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 6.0.0
>
>
> 1) izpack does not make the startserver, stopserver, scripts as executable in the linux
> 2) There is no option for *not* starting the server (either way it does not look like starting the server). This option should be extended to "setupmm" driven process too, with additional property.
> 3) multicast port is not available in the IZpack + it is hard coded; Any two machines are seeing each other on the same multicast address. This needs to be fixed as soon as possible.(FEDERATE-340)
> 4) System name is always defaulting to $hostname, even when it is blank. I fixed this in install.
> 5) With "systenhostsetup.sh" I can not pass in the properties file, it is looking for the file in a fixed location.
> 6) systemhostsetup.sh creates the "metamatrix.properties" file, but does not write to the configuration about what it's config name is, thus never can be started.
--
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
15 years, 9 months
[JBoss JIRA] Created: (TEIID-384) Remove the ValidateCriteriaVisitor
by Steven Hawkins (JIRA)
Remove the ValidateCriteriaVisitor
----------------------------------
Key: TEIID-384
URL: https://jira.jboss.org/jira/browse/TEIID-384
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.0.0
The ValidateCriteriaVisitor is enforcing a confusing restricting on searchability - based upon virtual layer metadata and only for the user query. This is meaningless since the searchability should actually be associated with the datatype. With our runtime types the only restrictions are on
BLOB - not searchable
CLOB - searchable like
XML - not searchable
OBJECT - not searchable
These should be imposed appropriately by the ValidationVisitor. Searchability metadata will then only be used to determine pushdown eligibility.
--
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
15 years, 9 months