December 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1926) Import from XML File Source skips wizard page "XML Data File Import Options" on MacOS

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1926?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1926. ------------------------------------ Resolution: Rejected Imported XML file was actually. Testing with xml file resulted in successful import. marking as rejected. > Import from XML File Source skips wizard page "XML Data File Import Options" on MacOS > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1926 > URL: https://issues.jboss.org/browse/TEIIDDES-1926 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3 > Environment: java 1.6 apple, JBDS 7, MacOS 10.8 > Reporter: Lucie Fabrikova > Assignee: Lucie Fabrikova > Fix For: 8.3 > > Attachments: accounts.xml, macos-xml-import-jdk1.6.png > > > Importing from XML file source on MacOS via importer wizard shows following pages: > "XML Data File Source Selection" - after setting all data and clicking on Next, page "View Model Definition" is showed - viz attachment. The Next button is disabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1926) Import from XML File Source skips wizard page "XML Data File Import Options" on MacOS

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1926?page=com.atlassian.jira.plu... ] Lucie Fabrikova edited comment on TEIIDDES-1926 at 12/5/13 9:29 AM: -------------------------------------------------------------------- Verified in Teiid Designer 8.3.0.CR1. was (Author: lfabriko): Verified in Teiid Designer 8.3.0.Beta3. > Import from XML File Source skips wizard page "XML Data File Import Options" on MacOS > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1926 > URL: https://issues.jboss.org/browse/TEIIDDES-1926 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3 > Environment: java 1.6 apple, JBDS 7, MacOS 10.8 > Reporter: Lucie Fabrikova > Assignee: Lucie Fabrikova > Fix For: 8.3 > > Attachments: accounts.xml, macos-xml-import-jdk1.6.png > > > Importing from XML file source on MacOS via importer wizard shows following pages: > "XML Data File Source Selection" - after setting all data and clicking on Next, page "View Model Definition" is showed - viz attachment. The Next button is disabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1926) Import from XML File Source skips wizard page "XML Data File Import Options" on MacOS

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1926?page=com.atlassian.jira.plu... ] Lucie Fabrikova commented on TEIIDDES-1926: ------------------------------------------- Verified in Teiid Designer 8.3.0.Beta3. > Import from XML File Source skips wizard page "XML Data File Import Options" on MacOS > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1926 > URL: https://issues.jboss.org/browse/TEIIDDES-1926 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3 > Environment: java 1.6 apple, JBDS 7, MacOS 10.8 > Reporter: Lucie Fabrikova > Assignee: Lucie Fabrikova > Fix For: 8.3 > > Attachments: accounts.xml, macos-xml-import-jdk1.6.png > > > Importing from XML file source on MacOS via importer wizard shows following pages: > "XML Data File Source Selection" - after setting all data and clicking on Next, page "View Model Definition" is showed - viz attachment. The Next button is disabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1966) Failed in Making a Multi-source Binding

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1966?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1966. ------------------------------------ Resolution: Done Restested with Mark's fix. Works great with our without server connection. > Failed in Making a Multi-source Binding > --------------------------------------- > > Key: TEIIDDES-1966 > URL: https://issues.jboss.org/browse/TEIIDDES-1966 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.2 > Environment: Mac OS X 10.9, Eclipse > Reporter: yapeng shen > Assignee: Mark Drilling > Labels: regression > Fix For: 8.3 > > > I've found out the multi-source binding support section in Teiid Designer User Guide 8.2, Chapter 9. > > In my testing project, I made a flat file data source and model. It's OK to query through VDB. Then I wanted to integrate another flat file in the same schema, which can be applied with multi-source binding support. > > As the User Guide pdf said, I clicked the VDB editor's Model tab, and then Source Binding Definition tab. I clicked the Multi-source check box and added a new source. Then a new tuple was added in the table, but among the three columns(source name, JNDI Name and Translator Name), only one can be edited till eclipse turns into a no-response state. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1979) Changes to a table's columns can result in role being reset for the entire model - 7.7.x

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1979?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1979: ---------------------------------------- Clone to handle 7.7.x patch release > Changes to a table's columns can result in role being reset for the entire model - 7.7.x > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-1979 > URL: https://issues.jboss.org/browse/TEIIDDES-1979 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7, 8.2 > Reporter: Marc Shirley > Assignee: Johnathon Lee > Fix For: 7.7.5 > > > I have a model like below with a role defined to remove read privileges on 'column1a2' only. > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> column1b2 > I adjust the model to rename 'column1b2' to 'uselessColumn': > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> uselessColumn > The role is reset and now has default read privileges defined across the entire model. I have to manually edit the role to reset it to the prior defined permissions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1864) Changes to a table's columns can result in role being reset for the entire model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1864?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1864: ----------------------------------- Fix Version/s: (was: 8.3) > Changes to a table's columns can result in role being reset for the entire model > -------------------------------------------------------------------------------- > > Key: TEIIDDES-1864 > URL: https://issues.jboss.org/browse/TEIIDDES-1864 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7, 8.2 > Reporter: Marc Shirley > Assignee: Johnathon Lee > Fix For: 7.7.5 > > Attachments: DataRoleResolver.patch > > > I have a model like below with a role defined to remove read privileges on 'column1a2' only. > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> column1b2 > I adjust the model to rename 'column1b2' to 'uselessColumn': > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> uselessColumn > The role is reset and now has default read privileges defined across the entire model. I have to manually edit the role to reset it to the prior defined permissions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1864) Changes to a table's columns can result in role being reset for the entire model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1864?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1864. ------------------------------------ Resolution: Done See TEIIDDES-1979 for 7.7.x > Changes to a table's columns can result in role being reset for the entire model > -------------------------------------------------------------------------------- > > Key: TEIIDDES-1864 > URL: https://issues.jboss.org/browse/TEIIDDES-1864 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7, 8.2 > Reporter: Marc Shirley > Assignee: Johnathon Lee > Fix For: 8.3 > > Attachments: DataRoleResolver.patch > > > I have a model like below with a role defined to remove read privileges on 'column1a2' only. > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> column1b2 > I adjust the model to rename 'column1b2' to 'uselessColumn': > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> uselessColumn > The role is reset and now has default read privileges defined across the entire model. I have to manually edit the role to reset it to the prior defined permissions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1864) Changes to a table's columns can result in role being reset for the entire model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1864?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1864: ----------------------------------- Fix Version/s: 8.3 (was: 7.7.5) > Changes to a table's columns can result in role being reset for the entire model > -------------------------------------------------------------------------------- > > Key: TEIIDDES-1864 > URL: https://issues.jboss.org/browse/TEIIDDES-1864 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7, 8.2 > Reporter: Marc Shirley > Assignee: Johnathon Lee > Fix For: 8.3 > > Attachments: DataRoleResolver.patch > > > I have a model like below with a role defined to remove read privileges on 'column1a2' only. > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> column1b2 > I adjust the model to rename 'column1b2' to 'uselessColumn': > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> uselessColumn > The role is reset and now has default read privileges defined across the entire model. I have to manually edit the role to reset it to the prior defined permissions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1979) Changes to a table's columns can result in role being reset for the entire model - 7.7.x

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1979: -------------------------------------- Summary: Changes to a table's columns can result in role being reset for the entire model - 7.7.x Key: TEIIDDES-1979 URL: https://issues.jboss.org/browse/TEIIDDES-1979 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.7, 8.2 Reporter: Marc Shirley Assignee: Johnathon Lee Fix For: 8.3, 7.7.5 I have a model like below with a role defined to remove read privileges on 'column1a2' only. model1 -> table1a ---> column1a1 ---> column1a2 -> table1b ---> column1b1 ---> column1b2 I adjust the model to rename 'column1b2' to 'uselessColumn': model1 -> table1a ---> column1a1 ---> column1a2 -> table1b ---> column1b1 ---> uselessColumn The role is reset and now has default read privileges defined across the entire model. I have to manually edit the role to reset it to the prior defined permissions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1979) Changes to a table's columns can result in role being reset for the entire model - 7.7.x

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1979?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1979: ----------------------------------- Fix Version/s: (was: 8.3) > Changes to a table's columns can result in role being reset for the entire model - 7.7.x > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-1979 > URL: https://issues.jboss.org/browse/TEIIDDES-1979 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7, 8.2 > Reporter: Marc Shirley > Assignee: Johnathon Lee > Fix For: 7.7.5 > > > I have a model like below with a role defined to remove read privileges on 'column1a2' only. > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> column1b2 > I adjust the model to rename 'column1b2' to 'uselessColumn': > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> uselessColumn > The role is reset and now has default read privileges defined across the entire model. I have to manually edit the role to reset it to the prior defined permissions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2013