August 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3645) Upgrade of Amazon aws sdk version

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3645?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3645: ---------------------------------- Fix Version/s: 8.12 (was: 8.11.3) > Upgrade of Amazon aws sdk version > --------------------------------- > > Key: TEIID-3645 > URL: https://issues.jboss.org/browse/TEIID-3645 > Project: Teiid > Issue Type: Component Upgrade > Components: Misc. Connectors > Affects Versions: 8.11.2 > Environment: teiid 8.11.2 > windows 8.1 > java 8 > Reporter: avinash misra > Assignee: Steven Hawkins > Fix For: 8.12 > > > I was working on dynamodb connector with latest dynamodb sdk. > This sdk uses aws-java-sdk-core version 1.10.11 but teiid uses aws-java-sdk 1.5.7. internally for simple db connector. > Could you please upgrade the aws sdk version to latest? > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[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: ------------------------------------- >>Looking at the difference of changes, you recognize the repeatability of configuring a translator/connector, transaction mgr, etc. And when any developer is building custom code, I would >>conclude they would do it in a manner for reuse across their deployments. So why not provide the framework for reuse without coding Van, what we are saying is you are making huge assumptions about the end user environment, and locking them in certain type of transaction manager, connector layer etc. If you are thinking you are providing an abstraction layer over these, that could be highly dependent upon the underlying frameworks and not easy enough generalize. In way you are set out to develop a configuration framework like Spring Bean framework. Google Guice is another example of such frameworks. In the end, since we can not make assumptions about the user environment, this as this does not provide much advantages and also developers are much more opinionated when using such frameworks. The best possible thing we can do is provide a good API and examples. > 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

1
0
0 / 0

[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: --------------------------------------- > if they are are making it parameterized, so that it is portable, then they all end up doing the same thing the framework is providing. So why not provide it for them. I don't think we're looking at this the same way. Underlying where you are coming from is something like "if I make assumptions x,y,z and include a new configuration framework, then for a class of embedded deployments people will have less work". While I'm saying that I don't want the project to assume responsibility for another configuration framework if possible, don't want to make assumptions about what dependencies are needed (especially if we just end up providing major portions of the AS anyway such as the JCA/pooling/transaction manager - as that would imply we should just embed the AS), and we can't really say that the class of embedded deployments that we'll end up addressing even represents a majority of what developers are trying to do. So I'm saying we should proceed with caution down this path. The more code that is being dedicated toward this on our end, the more likely it is that we are doing something wrong. > 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

1
0
0 / 0

[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: ------------------------------------ As for the connectors, its the examples that demonstrate it. The framework only provides it as an option, not a requirement. > 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

1
0
0 / 0

[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: ------------------------------------ > And when any developer is building custom code, I would conclude they would do it in a manner for reuse across their deployments. Yes, and what they end up with would be a jar / maven build, which is of course reusable. - if they are are making it parameterized, so that it is portable, then they all end up doing the same thing the framework is providing. So why not provide it for them. > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-3651) misc performance enhancements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3651?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3651: --------------------------------------- I also have changes to effectively remove the usage of java serialization from the client server protocol. However it will take more work to make them version compatible. > 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

1
0
0 / 0

[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: --------------------------------------- > configuring a translator It would probably be best to move in a direction that makes embedded and the server more similar (have embedded support for vdb based translator overrides), rather than introducing an alternative configuration. > connector That is heavily dependent on the JCA layer, it is not something we can generalize on our side unless you assume no JCA or embed one - the latter moves us more in the direction of just embedded wildfly/swarm. > transaction mgr Same as above. > And when any developer is building custom code, I would conclude they would do it in a manner for reuse across their deployments. Yes, and what they end up with would be a jar / maven build, which is of course reusable. > So why not provide the framework for reuse without coding. Because I don't believe that we can generally provide that 1. without assuming a lot of responsibility in kitting and runtime features which are provided by the AS or 2. by making too many assumptions such that what we provide won't be a good fit for a large number of scenarios. > 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

1
0
0 / 0

[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: ------------------------------------ I disagree. Looking at the difference of changes, you recognize the repeatability of configuring a translator/connector, transaction mgr, etc. And when any developer is building custom code, I would conclude they would do it in a manner for reuse across their deployments. So why not provide the framework for reuse without coding. > 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

1
0
0 / 0

[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: --------------------------------------- Sure. I'd also say then work TEIID-3541 first before thinking about what another repo would look like. > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-3650) Split Teiid Embedded into its own repo

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3650?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3650: ------------------------------------ Its being discussed that the projects should provide a BOM. Would this be a good time to create a BOM project just for that declaration? > 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2015