September 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2435) [Usability] The default user when connecting to server should be blanked out

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2435?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2435: ----------------------------------- Fix Version/s: 9.3 (was: 9.2) > [Usability] The default user when connecting to server should be blanked out > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2435 > URL: https://issues.jboss.org/browse/TEIIDDES-2435 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Affects Versions: 9.0.1 > Reporter: Van Halbert > Assignee: Paul Richardson > Fix For: 9.3 > > > In old versions of the Teiid server, the username "user" was the default. However, with newer versions, there is no default installed user. The person installing has to set that username. Therefore, its requested that the username in Teiid Designer be blanked our so that it eliminates confusion with prior versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2427) Add Geometry Type

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2427?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2427: ----------------------------------- Fix Version/s: 9.3 (was: 9.2) > Add Geometry Type > ----------------- > > Key: TEIIDDES-2427 > URL: https://issues.jboss.org/browse/TEIIDDES-2427 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration > Reporter: luca gioppo > Assignee: Barry LaFond > Labels: spatial, types > Fix For: 9.3 > > > As part of TEIID-2384 a geometry type has been added to Teiid (blob + srid int) with associated system and pushdown logic. Designer should add support for the new type as well. We need to coordinate on the type uuid as that will bridge between Teiid and Designer. Currently Teiid just modified the blob identifier - https://github.com/teiid/teiid/blob/master/engine/src/main/resources/org/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2664) Add OPTIONS capability to Procedure ResultSet

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2664?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2664: ------------------------------------------ > Steven Hawkins Is this defined in your current BNF? Yes, it will be. > Guess this also mean that you are adding extension properties, but since the "RETURNS" can be a raw type value OR a TABLE, it would mean adding them as extension props to the RESULT SET AND an "RESULT" parameter? Yes, it means that the properties will be on the resultset or on the result parameter. > Add OPTIONS capability to Procedure ResultSet > --------------------------------------------- > > Key: TEIIDDES-2664 > URL: https://issues.jboss.org/browse/TEIIDDES-2664 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Reporter: Ramesh Reddy > > Teiid DDL now supports options for procedure/functions returns clause parameters: > ... RETURNS (options ...) type > ... RETURNS (options ...) TABLE (...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2668) Add OPTIONS capability to Procedure ResultSet

by Steven Hawkins (JIRA)

Steven Hawkins created TEIIDDES-2668: ---------------------------------------- Summary: Add OPTIONS capability to Procedure ResultSet Key: TEIIDDES-2668 URL: https://issues.jboss.org/browse/TEIIDDES-2668 Project: Teiid Designer Issue Type: Enhancement Components: Teiid Integration Reporter: Ramesh Reddy Teiid DDL now supports options for procedure/functions returns clause parameters: ... RETURNS (options ...) type ... RETURNS (options ...) TABLE (...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2661) Add support for DATE/TIME/TIMESTAMP keyword literals

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2661?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2661: ----------------------------------- Fix Version/s: 9.3 > Add support for DATE/TIME/TIMESTAMP keyword literals > ---------------------------------------------------- > > Key: TEIIDDES-2661 > URL: https://issues.jboss.org/browse/TEIIDDES-2661 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Reporter: Steven Hawkins > Fix For: 9.3 > > > As per the spec we should support the literal format: > DATE '...' > TIME '...' > TIMESTAMP '...' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2665) Add an option to not widen comparisons to string

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2665?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2665: ----------------------------------- Fix Version/s: 9.3 > Add an option to not widen comparisons to string > ------------------------------------------------ > > Key: TEIIDDES-2665 > URL: https://issues.jboss.org/browse/TEIIDDES-2665 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Teiid Integration > Reporter: Steven Hawkins > Fix For: 9.3 > > > Our resolving logic considers anything with an implicit conversion to string to be a valid widening conversion in a comparison. For example: > int_col = '1a' > will effectively become cast(int_col as string) = '1a' > Or with timestamps: > timestamp_col = '1970-01-01' > becomes cast(timestamp_col as string) = '1970-01-01' > In equality cases the optimizer will infer that the predicate is simply false, but when used with greater/less than comparison we'll still attempt the query with the widening conversion. > This is most likely not the intent of the user. It would be best to provide an option that would allow an exception to be thrown rather than assuming a query that may not match the user's expectations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2664) Add OPTIONS capability to Procedure ResultSet

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2664?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2664: ---------------------------------------- [~shawkins] Is this defined in your current BNF? (https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL...) If it's a change to your BNF, then the Teiid DDL parser needs to be upgraded in Modeshape to account for the new grammar, else the Parsing for that statement will probably fail. You can test it easily enough in Designer using the DDL Importer with Teiid dialect option. Guess this also mean that you are adding extension properties, but since the "RETURNS" can be a raw type value OR a TABLE, it would mean adding them as extension props to the RESULT SET AND an "RESULT" parameter? This is because our EMF relational metamodel doesn't map directly to your DDL for procedures. > Add OPTIONS capability to Procedure ResultSet > --------------------------------------------- > > Key: TEIIDDES-2664 > URL: https://issues.jboss.org/browse/TEIIDDES-2664 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Reporter: Ramesh Reddy > > Teiid DDL now supports options for procedure/functions returns clause parameters: > ... RETURNS (options ...) type > ... RETURNS (options ...) TABLE (...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2536) No connection to Teiid instance after starting DV from JBDS - refresh needed

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2536?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2536: ---------------------------------------- [~mmakovy] The actual connection to the Teiid server doesn't take long at all. To be useful, the Teiid Server component in Designer is retrieving the Data Source, Translator and VDB information so the Teiid Server contents contain viable information. So depending on the number of data sources and VDBs deployed on your server, it may take 10 seconds to perform the necessary CLI calls. > No connection to Teiid instance after starting DV from JBDS - refresh needed > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2536 > URL: https://issues.jboss.org/browse/TEIIDDES-2536 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.2 > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 9.0.4, 9.2 > > Attachments: Screen Shot 2015-05-20 at 9.40.55 AM.png, Screen Shot 2015-05-20 at 9.41.04 AM.png > > > When you start DV server from JBDS there is no connection established to Teiid instance. You have to refresh server or Teiid Instance. Sometimes it is sufficient to expand particular server node in Servers view. > I think this issue is releated to TEIIDDES-2512 > Screenshots attached -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2667) Teiid Des has new requirement of Bouncy Castle

by Paul Leacu (JIRA)

Paul Leacu created TEIIDDES-2667: ------------------------------------ Summary: Teiid Des has new requirement of Bouncy Castle Key: TEIIDDES-2667 URL: https://issues.jboss.org/browse/TEIIDDES-2667 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 9.0.4 Reporter: Paul Leacu Priority: Blocker The 9.0.4.CR1 capture of Teiid Designer causes the Bouncy Castle install challenge dialog to appear. BC cryptographic technology appears to fall under US ITAR restrictions. Need to remove BC requirement from Teiid Des as was done for Fuse Tooling. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2665) Add an option to not widen comparisons to string

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2665?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2665: ------------------------------------------ TEIID-3722 added an option to now widen comparisons as described above. It would be desirable for Designer to support this behavior as well - and we may make it the default behavior starting with Teiid 9. > Add an option to not widen comparisons to string > ------------------------------------------------ > > Key: TEIIDDES-2665 > URL: https://issues.jboss.org/browse/TEIIDDES-2665 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Teiid Integration > Reporter: Steven Hawkins > > Our resolving logic considers anything with an implicit conversion to string to be a valid widening conversion in a comparison. For example: > int_col = '1a' > will effectively become cast(int_col as string) = '1a' > Or with timestamps: > timestamp_col = '1970-01-01' > becomes cast(timestamp_col as string) = '1970-01-01' > In equality cases the optimizer will infer that the predicate is simply false, but when used with greater/less than comparison we'll still attempt the query with the widening conversion. > This is most likely not the intent of the user. It would be best to provide an option that would allow an exception to be thrown rather than assuming a query that may not match the user's expectations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2015