November 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4505) Clarify JDG doc's

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4505?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4505. ----------------------------------- Resolution: Done Merged the pull request. > Clarify JDG doc's > ----------------- > > Key: TEIID-4505 > URL: https://issues.jboss.org/browse/TEIID-4505 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 9.2 > > > In the JDG related doc's, clarify the following: > JDG Hot Rod connector > - when defining the cacheTypeMap, the pfKeyField name should correspond to a getter/setter method in the pojo. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4437) Convert Teiid build to use "feature-pack"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4437?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4437: --------------------------------------- There are also some failures when running the arquillian tests, which we'll need to address as well. > Convert Teiid build to use "feature-pack" > ----------------------------------------- > > Key: TEIID-4437 > URL: https://issues.jboss.org/browse/TEIID-4437 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Ramesh Reddy > Assignee: Kylin Soong > Fix For: 9.2 > > > Change the current build process to build "feature-packs" for project, and then based on feature pack, build > - WildFly Server distribution > -WildFly Server Overlay distribution > Teiid currently have distributions, but not based on feature-packs, they need to be. Other distributions like AdminShell do not fall into this category. Only distributions that has WF involvement need a feature -pack (this is important to remember). > Currently Teiid uses "kit" directory in many different projects along with "wildfly-dist.xml" to populate "modules" directory. A feature-pack does EXACTLY same thing, but more with checks and balances. A feature pack, makes sure all the dependencies are met based on module.xml and module.xml defines the maven artifact rather than JAR file. i.e. it defines a metadata file, from which it can be build the zip file that "wildfly-dist.xml" assembly is currently doing. It also can has capabilities to "configure" the WF subsystem. That is manually done or done through CLI currently, using this part will be new. > Implementation Rules > 1) Every where we have "kit" directory, that module REQUIRES a "feature-pack" module. That means, every translator and resource-adapter gets it's own, and Teiid engine modules separately gets its own module. The reason to keep/create multiple modules is STRICTLY to keep the "modules" directory in feature-pack aligned ONE TO ONE with project that feature-pack represents. Otherwise, as developer we will NOT know which project is bringing in certain dependency, if all the modules are in single place. So, this is more about management of dependencies in a sane way. (Teiid did have all the modules in once place before in 7.x/8.x time, it is a nightmare to handle growing dependencies with our translators) > 2) NONE of the work we have is useless/or need to be redone, most everything we have PERFECTLY maps to this effort, except for for configuration part. > 3) For translator and resource adapter pair, I recommend that we pull them into single sub folder, and create a single feature pack for it. For example: > we have > {code} > connectors/translator-mongodb > connectors/connector-mongodb > {code} > I would like see we design as > {code} > connectors > /mongdb > /translator-mongodb > /connector-mongodb > /feature-pack-mongodb > {code} > No need to create "dist" packages for any resource-adapters or translators. As I mentioned in the beginning of the issue, there are two distributions, they are built using these various feature-packs. > 4) I would like to see a clean move of "kit/wildfly/modules" to "feature-packs" using "git", NOT CUT n PASTE where we loose the GIT history. This will preserve the confidence that what we have currently is EXACTLY same as in future with feature-packs. > 5) When designing the "feature-pack" projects, they ABSOLUTELY MUST NOT define any dependencies in their pom.xml other than Teiid project(s) they represent and any other feature-pack they refer to. (Kylin this is what cause most concern from your design for me) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4491) Refine uniqueidentifier support for SQL Server

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4491?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4491: --------------------------------- Fix Version/s: 8.12.8.6_3 > Refine uniqueidentifier support for SQL Server > ---------------------------------------------- > > Key: TEIID-4491 > URL: https://issues.jboss.org/browse/TEIID-4491 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.10.6_2, 8.12.8.6_3 > > > SQL Servers later than 2000 can treat uniqueidentifier as a comparable type - there is no need to always cast. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4552) Missing support for connection to Facebook via OAuth 2

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4552?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4552: ------------------------------- Fix Version/s: 9.2 > Missing support for connection to Facebook via OAuth 2 > ------------------------------------------------------ > > Key: TEIID-4552 > URL: https://issues.jboss.org/browse/TEIID-4552 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.12.5 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 9.2 > > Attachments: facebook3-vdb.xml, query, server.log, standalone.xml, teiid-oauth-util.sh-output > > > I would like to connect to facebook resource adapter and configure OAuth 2 security domain for it; I used teiid-oauth-util.sh to generate the security domain (see attachment). Facebook doesn't support refresh tokens and in the generated code is refresh token's value "null". > If I try to execute VDB with source pointing to such resource adapter I get error: > ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) Connector worker process failed for atomic-request=Gapuea1/NRcn.6.3.0: org.apache.cxf.rs.security.oauth2.provider.OAuthServiceException > > (see server.log, facebook-vdb.xml, standalone.xml) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4486) Improve performance of st_extent

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4486?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4486: --------------------------------- Fix Version/s: 8.12.8.6_3 > Improve performance of st_extent > -------------------------------- > > Key: TEIID-4486 > URL: https://issues.jboss.org/browse/TEIID-4486 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 9.0, 8.12.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.5, 8.12.8.6_3 > > > The implementation of st_extent is very costly. It should instead be based upon the Envelope class. Also it is not being pushed to pg. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4471) Assertion error with temp table delete

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4471?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4471: --------------------------------- Fix Version/s: 8.12.8.6_3 > Assertion error with temp table delete > -------------------------------------- > > Key: TEIID-4471 > URL: https://issues.jboss.org/browse/TEIID-4471 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.1, 8.13.7, 9.0.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.13.7, 9.0.5, 8.12.8.6_3 > > > Related to TEIID-4405 there are circumstances where a temp table deletion results in an assertion error of "delete failed". A possible scenario (that is dependent upon a number of factors, including batch sizes and garbage collection) requires the values stored by the tuple browser to get out of sync with what is stored by the page such that a delete is attempted twice. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4448) Multi-way join predicate inappropriately removed

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4448?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4448: --------------------------------- Fix Version/s: 8.12.8.6_3 > Multi-way join predicate inappropriately removed > ------------------------------------------------ > > Key: TEIID-4448 > URL: https://issues.jboss.org/browse/TEIID-4448 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.1, 8.13.7, 9.0.5, 8.7.10.6_2, 8.12.8.6_3 > > > In a situation where copy criteria can work against a multi-way join predicate, such that the predicate is not pushed: > t1.a = coalesce(t2.b, t3.c, t4.d) ... t1.a = t4.d > The multi-way predicate can be marked as optional and removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4393) Add new Geospatial functions

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4393?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4393: --------------------------------- Fix Version/s: 8.12.8.6_3 > Add new Geospatial functions > ---------------------------- > > Key: TEIID-4393 > URL: https://issues.jboss.org/browse/TEIID-4393 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.12.x, 9.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.1, 8.12.8.6_3 > > > Adding a list of geospatial features to be added. Used the following specification: https://portal.opengeospatial.org/files/?artifact_id=829 > st_Dimension > st_GeometryType > st_IsEmpty > st_IsSimple > st_Boundary > st_Envelope > st_X > st_Y > st_StartPoint > st_EndPoint > st_Boundary > st_Boundary > st_Length > st_NumPoints > st_PointN > st_Centroid > st_PointOnSurface > st_Area > st_ExteriorRing > st_NumInteriorRings > st_InteriorRingN > st_NumGeometries > st_GeometryN > st_IsClosed > st_Length > st_Centroid > st_PointOnSurface > st_Area > st_Within > st_Relate > st_Intersection > st_Difference > st_Union > st_SymmetricDifference > st_Buffer > st_ConvexHull -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4563) Too much COMMAND_LOG

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4563?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4563: --------------------------------------- In all of the configurations we provide org.teiid.COMMAND_LOG should be set to the warn level by default. Can you double check the logging configuration? > Too much COMMAND_LOG > -------------------- > > Key: TEIID-4563 > URL: https://issues.jboss.org/browse/TEIID-4563 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 9.2 > Reporter: Kylin Soong > Assignee: Steven Hawkins > Fix For: 9.2 > > Attachments: server.log.zip > > > I have found each query will generate 2 INFO COMMAND_LOG as attached server log, also the mat table update with a time interval, if this configured a little small, there will be great number of logs generated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4516: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1385600|https://bugzilla.redhat.com/show_bug.cgi?id=1385600] from NEW to CLOSED > Add support for updating child objects > -------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 9.2 > > > 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)

9 years, 4 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 November 2016