May 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4936) Add to tool to generate Couchbase ddl

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4936?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4936: --------------------------------------- Yes, we need to consider new caching strategies. > Add to tool to generate Couchbase ddl > -------------------------------------- > > Key: TEIID-4936 > URL: https://issues.jboss.org/browse/TEIID-4936 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 9.3 > Reporter: Kylin Soong > Assignee: Steven Hawkins > Priority: Optional > Fix For: 10.x > > > The tools can generate ddl.sql, base one some default properties, like sampleSize, sampleKeyspaces, typedNameList, etc, -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4854) Google translator fails to update timestamp value reformatted after update

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4854?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4854: ---------------------------------- Component/s: Misc. Connectors Fix Version/s: 10.0 (was: 9.3) > Google translator fails to update timestamp value reformatted after update > -------------------------------------------------------------------------- > > Key: TEIID-4854 > URL: https://issues.jboss.org/browse/TEIID-4854 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.3, 8.12.10.6_3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 10.0 > > Attachments: gs-reformatted-timestamp.log > > > Cell of type timestamp is reformatted after an update. Data inserted from teiid are in format "yyyy-mm-dd hh:mm:ss[.fffffffff]", which is reformatted to "dd/mm/yyyy hh:mm:ss[.fffffffff]". Subsequent update of such row throws exception "Could not convert source column Source.smalla.timestampvalue to the expected runtime type timestamp". > Google spreadsheet locale was UK, timezone was set to Berlin. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4934) Allow importing VDBs with conflicting model

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4934?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4934: ---------------------------------- Component/s: Server Fix Version/s: 10.x > Allow importing VDBs with conflicting model > ------------------------------------------- > > Key: TEIID-4934 > URL: https://issues.jboss.org/browse/TEIID-4934 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 9.2.3 > Environment: * Wildfly 10 > * Teiid Server 9.2.3 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Fix For: 10.x > > > It should be possible to import a model via "_import-vdb_" that conflicts with other models also imported via "_import-vdb_" if the conflicting model has the same version. > This will allow greater model reuse, and not to have duplicated model definitions in multiple vdbs. > Example: > VDB 1: > <code> > <vdb name="OneVDB" version="1"> > <description>One VDB</description> > <import-vdb name=ConflictingVDB" version="1"/> > <import-vdb name="OtherVDB" version="1"/> > </code> > VDB 2: > <code> > <vdb name="TwoVDB" version="1"> > <description>TwoVDB</description> > <import-vdb name=ConflictingVDB" version="1"/> > <import-vdb name="YetOtherVDB" version="1"/> > </code> > VDB 3: > <code> > <vdb name="ThirdVDB" version="1"> > <description>Third VDB</description> > <import-vdb name=OneVDB" version="1"/> > <import-vdb name="TwoVDB" version="1"/> > </code> > Currently we cannot use the ThirdVDB as is, since there is a conflicting VDB (ConflictingVDB) defined in VDBS One and Two. > Since both are using the same version, it should be possible to ignore the conflict (via a property for example). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3907) Support compensating transactions for updatable non-XA sources

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3907?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3907: ------------------------------------- Fix Version/s: 10.x Assignee: (was: Kylin Soong) > Support compensating transactions for updatable non-XA sources > -------------------------------------------------------------- > > Key: TEIID-3907 > URL: https://issues.jboss.org/browse/TEIID-3907 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.x > Reporter: Van Halbert > Fix For: 10.x > > > The transaction manager will fully support xa with all xa sources and a single local transaction resource. Beyond that however there is no built-in support for compensating transactions with non-XA sources. There has been work in Narayana on compensating transactions though that could be used by custom web apps consuming Teiid. We would like to eventually offer compensating options for some of our updatable non-XA sources, but it hasn't had sufficient priority yet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3928) Usage with analytical platforms

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3928?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3928: ------------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) Assignee: Steven Hawkins (was: Kylin Soong) > Usage with analytical platforms > ------------------------------- > > Key: TEIID-3928 > URL: https://issues.jboss.org/browse/TEIID-3928 > Project: Teiid > Issue Type: Sub-task > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Steven Hawkins > Fix For: 10.x > > > We should promote analytical platforms, such as Spark/Hive/PrestoDB, with usages of Teiid/DV as a data loader (we support a wider variety of sources can have views that perform incoming transformation/filtering logic) and for top level integration (since we provide more robust client support, transaction support, and broader federation). This effort will include documentation, additional integration code, and sample code. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4938) CLI getVDB operation domain mode - result of the operation is not in "result" element

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4938: ----------------------------------- Summary: CLI getVDB operation domain mode - result of the operation is not in "result" element Key: TEIID-4938 URL: https://issues.jboss.org/browse/TEIID-4938 Project: Teiid Issue Type: Bug Affects Versions: 8.12.10.6_3, 9.3 Reporter: Juraj Duráni Assignee: Steven Hawkins Priority: Minor If user reads status of VDB in domain mode, result of the operation is not written in the "result" attribute, but in separate attribute. Executing same operation in standalone mode, result is in "result" element. {code:plain|title=Domain mode result} [domain@localhost:9990 /] /profile=full/subsystem=teiid:get-vdb(...) { "outcome" => "success", "result" => undefined, "server-groups" => {"main-server-group" => {"host" => {"master" => { "server-one" => {"response" => { "outcome" => "success", "result" => {... } }}, "server-two" => {"response" => { "outcome" => "success", "result" => {... } }} }}}} } {code} {code:plain|title=Standalone mode result} [standalone@localhost:9990 /] /subsystem=teiid:get-vdb(...) { "outcome" => "success", "result" => {... } } {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4162) Swagger: Add XML payload support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4162?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4162: ---------------------------------- Fix Version/s: Open To Community 10.x > Swagger: Add XML payload support > -------------------------------- > > Key: TEIID-4162 > URL: https://issues.jboss.org/browse/TEIID-4162 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.0 > Reporter: Ramesh Reddy > Fix For: Open To Community, 10.x > > > The initial version only added support for application/json, and support for application/xml based payloads needs to be added to the translator. > Note that the metadata about XML is not captured currently. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4350) Enable Swagger in Rest war can be more simpler

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4350?page=com.atlassian.jira.plugin... ] Kylin Soong resolved TEIID-4350. -------------------------------- Resolution: Rejected > Enable Swagger in Rest war can be more simpler > ---------------------------------------------- > > Key: TEIID-4350 > URL: https://issues.jboss.org/browse/TEIID-4350 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.1 > Reporter: Kylin Soong > Assignee: Kylin Soong > > Current we use asm to add swagger annotations on every rest method and endpoint, but there are possibility to enable swagger without annotations, [1] is cxf swagger feature implement this. More details of cxf swagger refer to [2], with swagger feature, rest service can enable swagger with a one line configure. > I have talked with a ws guy, resteasy may add a similar feature, so I create this issue to catch that, if resteasy swagger feature is enable, teiid rest service can be enhanced enormously: > * swagger init, OriginFilter code can be removed. > * asm based add swagger annotation code can be removed. > The only need to keep are swaggerUI and resteasy swagger related configure. > [1] https://github.com/apache/cxf/blob/master/rt/rs/description-swagger/src/m... > [2] http://cxf.apache.org/docs/swagger2feature.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4350) Enable Swagger in Rest war can be more simpler

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4350?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-4350: ------------------------------------ Resteasy not have this links of feature, In the 10.x(EAP 7) rest implementation still use resteasy, but the the ws guys seems focus on cxf, so in the 10.x, no requirement for this feature. > Enable Swagger in Rest war can be more simpler > ---------------------------------------------- > > Key: TEIID-4350 > URL: https://issues.jboss.org/browse/TEIID-4350 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.1 > Reporter: Kylin Soong > Assignee: Kylin Soong > > Current we use asm to add swagger annotations on every rest method and endpoint, but there are possibility to enable swagger without annotations, [1] is cxf swagger feature implement this. More details of cxf swagger refer to [2], with swagger feature, rest service can enable swagger with a one line configure. > I have talked with a ws guy, resteasy may add a similar feature, so I create this issue to catch that, if resteasy swagger feature is enable, teiid rest service can be enhanced enormously: > * swagger init, OriginFilter code can be removed. > * asm based add swagger annotation code can be removed. > The only need to keep are swaggerUI and resteasy swagger related configure. > [1] https://github.com/apache/cxf/blob/master/rt/rs/description-swagger/src/m... > [2] http://cxf.apache.org/docs/swagger2feature.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4506) Evaluate Logstash whether it can repleace JPA + EJB + RDBMS

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4506?page=com.atlassian.jira.plugin... ] Kylin Soong updated TEIID-4506: ------------------------------- Priority: Optional (was: Major) > Evaluate Logstash whether it can repleace JPA + EJB + RDBMS > ----------------------------------------------------------- > > Key: TEIID-4506 > URL: https://issues.jboss.org/browse/TEIID-4506 > Project: Teiid > Issue Type: Feature Request > Components: Tools > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Kylin Soong > Priority: Optional > Fix For: 10.x > > > * JPA + EJB + RDBMS + logAppender to persist logging is quite legacy way, JPA/Hibernate have performance bottleneck, it also consume high cpu and memory. > * https://www.elastic.co/products/logstash are a popular logging framework used in micro service, big data area, both Wildfly Swarm and Spring boot have support it. > So I think it may helpful to spend some time to investigate the Logstash, to check whether it can repleace current JPA + EJB + RDBMS way -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2017