[JBoss JIRA] (TEIID-3651) misc performance enhancements
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3651:
-------------------------------------
Summary: misc performance enhancements
Key: TEIID-3651
URL: https://issues.jboss.org/browse/TEIID-3651
Project: Teiid
Issue Type: Quality Risk
Components: JDBC Driver, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12
To improve socket performance, there are some quick changes that can be made.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3650) Split Teiid Embedded into its own repo
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3650?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3650:
---------------------------------------
At this point there are no modules that are embedded specific. There is a minor amount of code in the runtime that is embedded specific, but most is shared. The intrusion is mostly in building. TEIID-3541 covers removing the kit, however the issue there is with dependency management. We'd have to effectively duplicate all shared dependencies from the integration bom into an embedded specific bom - as well as fix / make consistent how we pull in dependencies for each of the modules that contributes to embedded. So I'm not sure what this would look especially if TEIID-3541 is worked unless you are thinking there will be a lot of embedded specific work.
> Split Teiid Embedded into its own repo
> --------------------------------------
>
> Key: TEIID-3650
> URL: https://issues.jboss.org/browse/TEIID-3650
> Project: Teiid
> Issue Type: Task
> Components: Embedded
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> Split Teiid Embedded into its own repo so that it can adapt easier to its own needs, independent of Teiid proper.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3649) Improve usability of Teiid Embedded
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3649?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3649:
-------------------------------------
+1 for [~shawkins] comments. Also there is no JCA layer to build this upon. Having a kit or not, does not provide any usability for embedded from community questions we have seen so far, and adding a translator and basic connection using programatically is pretty straight forward. The main idea behind Embedded is to "embed" into a foreign VM, where configuration/source connections, management apis, logging, security etc may have been already defined and Teiid Embedded needs to work with it.
IMO, usability can come from
- Improve the APIs
- Improve the documentation
- Improve the examples
BTW, my ideas behind the JDBC/ODBC kit using Teiid Embedded for a particular source will completely black box the concepts such VDB, translator, resource-adapter and just provide a single JAR with URL to connect to source, may be simple properties file if needed specific to source.
> Improve usability of Teiid Embedded
> -----------------------------------
>
> Key: TEIID-3649
> URL: https://issues.jboss.org/browse/TEIID-3649
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> The usability of Teiid Embedded needs to be improved so that it can be closer to OOTB for some of the basic use cases.
> The Teiid Embedded Driver discussion [1] is covering this topic with a possibility that there is an easier way to use Teiid Embedded without removing the capability to programmatically to use the tool.
> [1] https://developer.jboss.org/wiki/TeiidEmbeddedDriver
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3649) Improve usability of Teiid Embedded
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3649?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3649:
------------------------------------
The data driven framework doesn't preclude someone from doing any development that they would now. It just provides a framework for doing it once a then making it easier to reuse. Using the framework, you can then data drive its reuse, making redeployments of their code more of a packaged delivery.
> Improve usability of Teiid Embedded
> -----------------------------------
>
> Key: TEIID-3649
> URL: https://issues.jboss.org/browse/TEIID-3649
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> The usability of Teiid Embedded needs to be improved so that it can be closer to OOTB for some of the basic use cases.
> The Teiid Embedded Driver discussion [1] is covering this topic with a possibility that there is an easier way to use Teiid Embedded without removing the capability to programmatically to use the tool.
> [1] https://developer.jboss.org/wiki/TeiidEmbeddedDriver
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3650) Split Teiid Embedded into its own repo
by Van Halbert (JIRA)
Van Halbert created TEIID-3650:
----------------------------------
Summary: Split Teiid Embedded into its own repo
Key: TEIID-3650
URL: https://issues.jboss.org/browse/TEIID-3650
Project: Teiid
Issue Type: Task
Components: Embedded
Reporter: Van Halbert
Assignee: Steven Hawkins
Split Teiid Embedded into its own repo so that it can adapt easier to its own needs, independent of Teiid proper.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3649) Improve usability of Teiid Embedded
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3649?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3649:
---------------------------------------
Ideally this should not be phrased as improving the usability of Teiid Embedded in so much as creating more special use kits/configuration. The base usage for embedded will remain as Teiid without JBoss AS and requiring custom development to target a variety of other platforms depending upon the needs of the application. Other special use kits / configuration include providing a JDBC/ODBC driver tool kit - TEIID-2416.
We should proceed with caution in promoting a simpler to use embedded, which doesn't address kitting issues, introduces a custom configuration layer, still doesn't address specific deployment scenarios, mixes programmatic and file based configuration, etc. For example if we end up kitting everything including the JCA layer / transaction manager then it may make more sense to look at this as embedding wildfly or using swarm - which Kylin I think has been looking into.
Other related issues include TEIID-3367 and TEIID-3512
> Improve usability of Teiid Embedded
> -----------------------------------
>
> Key: TEIID-3649
> URL: https://issues.jboss.org/browse/TEIID-3649
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> The usability of Teiid Embedded needs to be improved so that it can be closer to OOTB for some of the basic use cases.
> The Teiid Embedded Driver discussion [1] is covering this topic with a possibility that there is an easier way to use Teiid Embedded without removing the capability to programmatically to use the tool.
> [1] https://developer.jboss.org/wiki/TeiidEmbeddedDriver
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3649) Improve usability of Teiid Embedded
by Van Halbert (JIRA)
Van Halbert created TEIID-3649:
----------------------------------
Summary: Improve usability of Teiid Embedded
Key: TEIID-3649
URL: https://issues.jboss.org/browse/TEIID-3649
Project: Teiid
Issue Type: Feature Request
Components: Embedded
Reporter: Van Halbert
Assignee: Steven Hawkins
The usability of Teiid Embedded needs to be improved so that it can be closer to OOTB for some of the basic use cases.
The Teiid Embedded Driver discussion [1] is covering this topic with a possibility that there is an easier way to use Teiid Embedded without removing the capability to programmatically to use the tool.
[1] https://developer.jboss.org/wiki/TeiidEmbeddedDriver
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (TEIID-3632) Performance issue retrieving data source and translator definitions through the AdminFactory
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3632?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3632:
----------------------------------
Fix Version/s: 8.12
Component/s: AdminApi
We'll look into on our side.
> Performance issue retrieving data source and translator definitions through the AdminFactory
> --------------------------------------------------------------------------------------------
>
> Key: TEIID-3632
> URL: https://issues.jboss.org/browse/TEIID-3632
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Reporter: Barry LaFond
> Assignee: Ramesh Reddy
> Fix For: 8.12
>
> Attachments: server_refresh_cli_log.txt
>
>
> Based on the issue described in TEIIDDES-2592, we discovered that connecting to a remote server that contained ~ 40 data sources required > 10 minutes to refresh the Server view in Teiid Designer. After some debugging it appeared that some of the current behavior in AdminFactory results multiple redundant CLI calls to retrieve intermediate information to compile even a simple list of data source names.
> In Teiid Designer, we modified our forked Admin8Factory to define a few cached sets of data that get cleared if data is changed by our ExecutionAdmin class for any created or deleted data sources.
> Note that Designer's Server management paradigm includes the requirement to view the DS/Translator/VDB contents on the server.
> So I'm assuming that there could be some benefit if Teiid AdminFactory adapted a similar approach to improving the performance/behavior of the internal methods of this class.
> see: https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/teii... for details
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months