May 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4536) Support create schema with multiple statements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4536?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4536: ------------------------------------- I would vote to defer this permanently :) > Support create schema with multiple statements > ---------------------------------------------- > > Key: TEIID-4536 > URL: https://issues.jboss.org/browse/TEIID-4536 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > Create schema can support following create statements being directly associated rather than requiring an intermediate use schema > create schema x > create view ... > ... > ; -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4536) Support create schema with multiple statements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4536?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4536: ---------------------------------- Fix Version/s: 10.0 (was: 9.3) Priority: Major (was: Critical) With the other metadata changes, we are moving back towards sequential loading of ddl. This issue is now more of a nice to have, rather than a requirement. The basic parsing changes are there - we just need to slim down the allowable statements and ensure that they run specifically in the scope of schema being created. > Support create schema with multiple statements > ---------------------------------------------- > > Key: TEIID-4536 > URL: https://issues.jboss.org/browse/TEIID-4536 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > Create schema can support following create statements being directly associated rather than requiring an intermediate use schema > create schema x > create view ... > ... > ; -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4902) Create embedded example for the new infinispan hotrod translator/connector

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4902?page=com.atlassian.jira.plugin... ] Work on TEIID-4902 started by Van Halbert. ------------------------------------------ > Create embedded example for the new infinispan hotrod translator/connector > -------------------------------------------------------------------------- > > Key: TEIID-4902 > URL: https://issues.jboss.org/browse/TEIID-4902 > Project: Teiid > Issue Type: Task > Components: Quick Starts > Affects Versions: 9.3 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > Create an embedded quickstart for the new infinispan hotrod connector/translator. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4903) Create a new server quickstart for the new infinispan hotrod connector/translator

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4903?page=com.atlassian.jira.plugin... ] Work on TEIID-4903 started by Van Halbert. ------------------------------------------ > Create a new server quickstart for the new infinispan hotrod connector/translator > --------------------------------------------------------------------------------- > > Key: TEIID-4903 > URL: https://issues.jboss.org/browse/TEIID-4903 > Project: Teiid > Issue Type: Task > Components: Infinispan, Quick Starts > Affects Versions: 9.3.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > Create a new server quickstart for the new infinispan hotrod connector/translator. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4895) Determine community requirements for WildFly usage

by Tom Arnold (JIRA)

[ https://issues.jboss.org/browse/TEIID-4895?page=com.atlassian.jira.plugin... ] Tom Arnold commented on TEIID-4895: ----------------------------------- We currently use (and have some tools built around) the combined Teiid/Wildfly artifact. > Determine community requirements for WildFly usage > -------------------------------------------------- > > Key: TEIID-4895 > URL: https://issues.jboss.org/browse/TEIID-4895 > Project: Teiid > Issue Type: Task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > WildFly is typically the runtime for Teiid. However we want feedback from the community on what style of WildFly integration is important: > - The ability to deploy Teiid into a managed WildFly instance/cluster > - The combination Teiid/WildFly artifact > - A layered docker image > - Not full WildFly, just Swarm > - Not needed, just Embedded > Based upon this we can better tune our documentation, downloads, and examples. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4051) Swagger metadata includes internal java constructs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4051: ---------------------------------- Fix Version/s: 10.0 (was: 9.3) > Swagger metadata includes internal java constructs > -------------------------------------------------- > > Key: TEIID-4051 > URL: https://issues.jboss.org/browse/TEIID-4051 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.x > Reporter: Steven Hawkins > Fix For: 10.0 > > > From IntegrationTestRestWarGeneration the swagger metadata includes definitions for Statement, ResultSet, StreamingOutput, etc.: > ... > InputStream: > type: "object" > Statement: > type: "object" > properties: > queryTimeout: > type: "integer" > format: "int32" > closed: > type: "boolean" > default: false > resultSet: > $ref: "#/definitions/ResultSet" > ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4253) Validate support for Google Cloud SQL

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4253?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4253: ---------------------------------- Issue Type: Task (was: Feature Request) Description: Validate support for Google Cloud SQL with mysql and postgresql connectivity. (was: Add support for Google Cloud SQL. ) Fix Version/s: 10.x (was: 9.3) Summary: Validate support for Google Cloud SQL (was: Add support for Google Cloud SQL) Changing to a validation task and pulling out of a release bucket. > Validate support for Google Cloud SQL > ------------------------------------- > > Key: TEIID-4253 > URL: https://issues.jboss.org/browse/TEIID-4253 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Fix For: Open To Community, 10.x > > > Validate support for Google Cloud SQL with mysql and postgresql connectivity. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4558) Query Plan Analyzer

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4558?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4558: ---------------------------------- Fix Version/s: Open To Community 10.0 (was: 9.3) > Query Plan Analyzer > ------------------- > > Key: TEIID-4558 > URL: https://issues.jboss.org/browse/TEIID-4558 > Project: Teiid > Issue Type: Feature Request > Components: Tools > Affects Versions: 9.2 > Reporter: Van Halbert > Fix For: Open To Community, 10.0 > > > Provide a tool that would take a query plan and provide feed back. > Example: > - indicate where there maybe a problem in the structure of the query that may impact performance > - indicate in the plan where there maybe issues (like table scan, no rows, etc.) > - provide recommendations for improving performance > etc.. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) Add support for updating child objects

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4516: ---------------------------------- Fix Version/s: (was: 9.3) Removing from 9.3. It's not clear what release these may belong in now that the JDG connectivity has been moved to it's own repository. > Add support for updating child objects > -------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: JDG Connector > Affects Versions: 8.12.7.6_3, 9.2 > Reporter: Jan Stastny > Assignee: Van Halbert > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4517) Add support for deleting child objects

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4517?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4517: ---------------------------------- Fix Version/s: (was: 9.3) Removing from 9.3. It's not clear what release these may belong in now that the JDG connectivity has been moved to it's own repository. > Add support for deleting child objects > -------------------------------------- > > Key: TEIID-4517 > URL: https://issues.jboss.org/browse/TEIID-4517 > Project: Teiid > Issue Type: Feature Request > Components: JDG Connector > Affects Versions: 8.12.7.6_3, 9.2 > Reporter: Jan Stastny > Assignee: Van Halbert > > Infinispan cache dsl translator currently doesn't support deleting child objects when using complex POJO classes. > Example of complex POJO: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > Mapped metadata: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Expected usage: > {code:sql} > DELETE FROM PhoneNumber WHERE id=3 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 May 2017