March 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2060) Cannot select encoding when file model execute preview data

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2060?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2060: ----------------------------------- Fix Version/s: 8.5 > Cannot select encoding when file model execute preview data > ----------------------------------------------------------- > > Key: TEIIDDES-2060 > URL: https://issues.jboss.org/browse/TEIIDDES-2060 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 8.3.1 > Reporter: Eiichi Nagai > Assignee: Barry LaFond > Priority: Blocker > Fix For: 8.5 > > > Teiid designer can select file encoding when create file model using import function. However, it does not effect preview data function and actual VDB. > Actual VDB can set encoding by overriding file translator property. However, VDB for preview data function is created by automatically in teiid designer, so we cannot set encoding. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2077) 8.5 Release Work

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2077: -------------------------------------- Summary: 8.5 Release Work Key: TEIIDDES-2077 URL: https://issues.jboss.org/browse/TEIIDDES-2077 Project: Teiid Designer Issue Type: Task Components: Release Work Affects Versions: 8.5 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.5 Basic jira for 8.5 release process. Documentation, versioning, etc... -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2076) Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2076?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2076: ------------------------------------------ This is initially a Teiid request, which will then need designer handling to match. I see two pieces that they are requesting: 1. Allow for a selector to be use with fixed width file - currently it is only for delimited files: https://docs.jboss.org/author/display/TEIID/FROM+Clause 2. (possibly obviated by 1) to make a best effort at returning rows with a fixed size, but the data is of a smaller length. And yes, a sample file would help ensure that we understand the format correctly. > Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2076 > URL: https://issues.jboss.org/browse/TEIIDDES-2076 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Barry LaFond > > Current behavior is that data lines too short to fit a fixed width data interpretation produces an error such as "Error: Text parse error: Fixed width line width 35 is smaller than the expected 60 on text line 1 in file:/tmp/file.csv.". The customer's use case is interpreting data files from another application which bundles multiple types of data along with additional descriptive info/metadata about the data contained within the file. As the error is thrown if any lines after the first interpreted line are shorter than the summed value of the fixed width columns, they are unable to query the file. The customer wishes for the ERROR to be suppressed and the query to return the data independent of whether it fits the fixed width criteria and potentially to be able to filter the data being retrieved. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2076) Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2076?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2076: ---------------------------------------- Not sure how this initially will affect Designer since it appears the issue is with how Teiid is reading the data based on the XMLTABLE() definition? Once Teiid decides if and how they handle it, there may or may not be tooling changes to accommodate them. Lastly, please provide a sample/snippet of an applicable data file? > Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2076 > URL: https://issues.jboss.org/browse/TEIIDDES-2076 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Barry LaFond > > Current behavior is that data lines too short to fit a fixed width data interpretation produces an error such as "Error: Text parse error: Fixed width line width 35 is smaller than the expected 60 on text line 1 in file:/tmp/file.csv.". The customer's use case is interpreting data files from another application which bundles multiple types of data along with additional descriptive info/metadata about the data contained within the file. As the error is thrown if any lines after the first interpreted line are shorter than the summed value of the fixed width columns, they are unable to query the file. The customer wishes for the ERROR to be suppressed and the query to return the data independent of whether it fits the fixed width criteria and potentially to be able to filter the data being retrieved. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1786) Update query metadata interface for update to teiid 8.5 interface

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1786?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1786: ----------------------------------- Fix Version/s: 8.5 > Update query metadata interface for update to teiid 8.5 interface > ----------------------------------------------------------------- > > Key: TEIIDDES-1786 > URL: https://issues.jboss.org/browse/TEIIDDES-1786 > Project: Teiid Designer > Issue Type: Task > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Minor > Fix For: 8.4, 8.5 > > > Per Steve Hawkins 7/17/2013: > https://issues.jboss.org/browse/TEIID-2365 for 8.5 removed the ResolverVisitor.setFindShortName method so that we don't have to rely on static/ThreadLocal logic. Instead this value can be set via the QueryMetadataInterface method findShortName. A simple usage pattern is: > QueryMetadataInterface metadata = new BasicQueryMetadataWrapper(metadata){ > public boolean useOutputName() { > return false; > }; > }; > QueryResolver.resolveCommand(command, metadata); > Or this could possibly integrated into your workspace metadata in an appropriate manner (considering thread-safe usage, etc.). -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2014) 8.4 Release Work

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2014?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2014. ------------------------------------ Resolution: Done 8.4 Released - 3/12/2014 > 8.4 Release Work > ---------------- > > Key: TEIIDDES-2014 > URL: https://issues.jboss.org/browse/TEIIDDES-2014 > Project: Teiid Designer > Issue Type: Task > Components: Release Work > Affects Versions: 8.4 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Blocker > Fix For: 8.4, 8.3.2 > > > Work related to 8.4.0 release including: > * Version upgrades > * Copyright changes > * build/publish > * documentation -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2076) Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-2076: ------------------------------------- Summary: Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length Key: TEIIDDES-2076 URL: https://issues.jboss.org/browse/TEIIDDES-2076 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.8 Reporter: Van Halbert Current behavior is that data lines too short to fit a fixed width data interpretation produces an error such as "Error: Text parse error: Fixed width line width 35 is smaller than the expected 60 on text line 1 in file:/tmp/file.csv.". The customer's use case is interpreting data files from another application which bundles multiple types of data along with additional descriptive info/metadata about the data contained within the file. As the error is thrown if any lines after the first interpreted line are shorter than the summed value of the fixed width columns, they are unable to query the file. The customer wishes for the ERROR to be suppressed and the query to return the data independent of whether it fits the fixed width criteria and potentially to be able to filter the data being retrieved. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2076) Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2076?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-2076: ---------------------------------- Assignee: Barry LaFond > Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2076 > URL: https://issues.jboss.org/browse/TEIIDDES-2076 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.8 > Reporter: Van Halbert > Assignee: Barry LaFond > > Current behavior is that data lines too short to fit a fixed width data interpretation produces an error such as "Error: Text parse error: Fixed width line width 35 is smaller than the expected 60 on text line 1 in file:/tmp/file.csv.". The customer's use case is interpreting data files from another application which bundles multiple types of data along with additional descriptive info/metadata about the data contained within the file. As the error is thrown if any lines after the first interpreted line are shorter than the summed value of the fixed width columns, they are unable to query the file. The customer wishes for the ERROR to be suppressed and the query to return the data independent of whether it fits the fixed width criteria and potentially to be able to filter the data being retrieved. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1634) For Komodo, remove UUID from the persisted models, will help with ability to merge models

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1634?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-1634: ---------------------------------- Assignee: Barry LaFond > For Komodo, remove UUID from the persisted models, will help with ability to merge models > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-1634 > URL: https://issues.jboss.org/browse/TEIIDDES-1634 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: Komodo > > > When saving a model file, don't persist the UUID's in the file. This would make the file smaller and help with the user's ability to manage their models in a SCM and merge the changes. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1635) Designer is not showing the same error in the server log

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1635?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-1635: ---------------------------------- Assignee: Barry LaFond > Designer is not showing the same error in the server log > -------------------------------------------------------- > > Key: TEIIDDES-1635 > URL: https://issues.jboss.org/browse/TEIIDDES-1635 > Project: Teiid Designer > Issue Type: Feature Request > Components: Usability > Affects Versions: 7.4 > Reporter: Van Halbert > Assignee: Barry LaFond > > JBoss developer studio is not returning complete error stack trace. For example, running a query throws error in the designer which is different from error in server log and we would like to get the error whatever is there in the server.log to troubleshoot and fix the issues. > It's really difficult for developers to understand and fix the issues with the way error is shown in the designer compared to more useful error shown in the server.log. -- 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

12 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2014