August 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2902) Deprecate XML Document Models

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2902?page=com.atlassian.jira.plu... ] Steven Hawkins reassigned TEIIDDES-2902: ---------------------------------------- Assignee: (was: Steven Hawkins) > Deprecate XML Document Models > ----------------------------- > > Key: TEIIDDES-2902 > URL: https://issues.jboss.org/browse/TEIIDDES-2902 > Project: Teiid Designer > Issue Type: Task > Reporter: Steven Hawkins > > With TEIID-4100 our OData v4 implementation provides most of the features provided by XML Document models. Between OData and SQL/XML as replacements, we need to formally deprecate the legacy XML approach. > Additional tasks include: > A way to perform OData queries from within the vdb > Optimizations to approximate the usage of staging tables -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2902) Deprecate XML Document Models

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2902?page=com.atlassian.jira.plu... ] Steven Hawkins updated TEIIDDES-2902: ------------------------------------- Component/s: Modeling Description: With TEIID-4100 our OData v4 implementation provides most of the features provided by XML Document models. Between OData and SQL/XML as replacements, we need to formally deprecate the legacy XML approach. (was: With TEIID-4100 our OData v4 implementation provides most of the features provided by XML Document models. Between OData and SQL/XML as replacements, we need to formally deprecate the legacy XML approach. Additional tasks include: A way to perform OData queries from within the vdb Optimizations to approximate the usage of staging tables ) > Deprecate XML Document Models > ----------------------------- > > Key: TEIIDDES-2902 > URL: https://issues.jboss.org/browse/TEIIDDES-2902 > Project: Teiid Designer > Issue Type: Task > Components: Modeling > Reporter: Steven Hawkins > > With TEIID-4100 our OData v4 implementation provides most of the features provided by XML Document models. Between OData and SQL/XML as replacements, we need to formally deprecate the legacy XML approach. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2902) Deprecate XML Document Models

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2902?page=com.atlassian.jira.plu... ] Steven Hawkins moved TEIID-4401 to TEIIDDES-2902: ------------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-2902 (was: TEIID-4401) Component/s: (was: Query Engine) Fix Version/s: (was: 9.1) > Deprecate XML Document Models > ----------------------------- > > Key: TEIIDDES-2902 > URL: https://issues.jboss.org/browse/TEIIDDES-2902 > Project: Teiid Designer > Issue Type: Task > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > With TEIID-4100 our OData v4 implementation provides most of the features provided by XML Document models. Between OData and SQL/XML as replacements, we need to formally deprecate the legacy XML approach. > Additional tasks include: > A way to perform OData queries from within the vdb > Optimizations to approximate the usage of staging tables -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2655) It is possible to create project with project name that is already in workspace folder

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2655?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2655. ------------------------------------ Resolution: Won't Fix This is default Eclipse behavior, though I think it's confusing and possibly dangerious. But we won't fix since we delegate to Eclipse's new project wizard. > It is possible to create project with project name that is already in workspace folder > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-2655 > URL: https://issues.jboss.org/browse/TEIIDDES-2655 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.4 > Environment: MAC OS X > Reporter: Matus Makovy > Fix For: 10.0.2 > > > I think Designer should not allow user to create project with same name that is already in workspace folder. > See steps to reproduce -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2876) Clean up wording in Stored Procedure Prompt

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2876?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2876. ------------------------------------ Resolution: Done 10.0.x: https://github.com/Teiid-Designer/teiid-designer/pull/555 > Clean up wording in Stored Procedure Prompt > ------------------------------------------- > > Key: TEIIDDES-2876 > URL: https://issues.jboss.org/browse/TEIIDDES-2876 > Project: Teiid Designer > Issue Type: Bug > Reporter: Steve Tran > Assignee: Barry LaFond > Priority: Minor > Fix For: 10.0.2 > > Attachments: bug.PNG > > > The wording on the Stored Procedure prompt contains grammatical typos. See screenshot of the issues. These messages are in a shared messages.properties file, so if there are other typos, we should clean those up as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2394) Add UI support for TEXTTABLE Custom Line Separator

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2394?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2394: ----------------------------------- Fix Version/s: 11.0 (was: 10.0.2) Adding this minor feature to will required teiid version customization due to includes in Teiid 8.10. Pushing to 11.0 to utilize Teiid 9.0 runtime src and functionality > Add UI support for TEXTTABLE Custom Line Separator > --------------------------------------------------- > > Key: TEIIDDES-2394 > URL: https://issues.jboss.org/browse/TEIIDDES-2394 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, Patch Release, Teiid Integration > Reporter: Shiveeta Mattoo > Assignee: Barry LaFond > Labels: FileConnector, TEXTTABLE > Fix For: 11.0 > > > Add UI support for TEXTTABLE capability to support a Custom Line Separator . See https://docs.jboss.org/author/display/TEIID/FROM+Clause with the ROW DELIMITER char option. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2796) Warning dialog when generating dynamic VDB is hardly readable

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2796?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2796. ------------------------------------ Resolution: Done 10.0.x: https://issues.jboss.org/browse/TEIIDDES-2796 > Warning dialog when generating dynamic VDB is hardly readable > ------------------------------------------------------------- > > Key: TEIIDDES-2796 > URL: https://issues.jboss.org/browse/TEIIDDES-2796 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Patch Release, Usability > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Minor > Fix For: 10.0.2 > > Attachments: Screenshot from 2016-02-26 15-21-32.png > > > The warning dialog that is shown when some models are omitted from a dynamic vdb has white text on gray background on linux, making the text very hard to read (see screenshot). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2335) Profile and analyze for memory leaks

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2335?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2335: ----------------------------------- Fix Version/s: 11.0 (was: 10.0.2) > Profile and analyze for memory leaks > ------------------------------------ > > Key: TEIIDDES-2335 > URL: https://issues.jboss.org/browse/TEIIDDES-2335 > Project: Teiid Designer > Issue Type: Task > Components: Usability > Affects Versions: 8.6 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 11.0 > > > Been quite some time since we did a memory analysis/check of Teiid Designer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2812. ------------------------------------ Resolution: Done Done > Add ability to reverse engineer into a Pojo object from a table or view > ----------------------------------------------------------------------- > > Key: TEIIDDES-2812 > URL: https://issues.jboss.org/browse/TEIIDDES-2812 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Usability > Affects Versions: 9.0.6 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > Fix For: 10.0.2 > > Attachments: jdg-module-generated-files.png, materialize-action.png, materialize-wizard-page-1.png, materialize-wizard-page-2.png, materialized-table-property-value.png > > > The scenario is: select table/view, right mouse click select Create Pojo, present dialog, need a file chooser to select location to save output. > Label of action: Create Pojo (or something to indicates the process) > Dialog title: Create Pojo from Table [tableName] > Message: This will create a Pojo class, and packaged in a jar, that is meant to be used when JDG will be used in materialization or accessed as a data source. > Options: > - file chooser option to select folder to save pojo jar > - drop-down: <select option> > Access JDG in Library Mode > Access JDG via Hot Rod Client > - pojo package name (default = org.teiid.pojo) > - pojo jar name (default = pojo.jar) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2812: ---------------------------------------- 10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/3691ad7443e6d9bf9... > Add ability to reverse engineer into a Pojo object from a table or view > ----------------------------------------------------------------------- > > Key: TEIIDDES-2812 > URL: https://issues.jboss.org/browse/TEIIDDES-2812 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Usability > Affects Versions: 9.0.6 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > Fix For: 10.0.2 > > Attachments: jdg-module-generated-files.png, materialize-action.png, materialize-wizard-page-1.png, materialize-wizard-page-2.png, materialized-table-property-value.png > > > The scenario is: select table/view, right mouse click select Create Pojo, present dialog, need a file chooser to select location to save output. > Label of action: Create Pojo (or something to indicates the process) > Dialog title: Create Pojo from Table [tableName] > Message: This will create a Pojo class, and packaged in a jar, that is meant to be used when JDG will be used in materialization or accessed as a data source. > Options: > - file chooser option to select folder to save pojo jar > - drop-down: <select option> > Access JDG in Library Mode > Access JDG via Hot Rod Client > - pojo package name (default = org.teiid.pojo) > - pojo jar name (default = pojo.jar) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2016