March 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2899) Limit cannot be pushed to the left side of a sideways correlated join

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2899: ------------------------------------- Summary: Limit cannot be pushed to the left side of a sideways correlated join Key: TEIID-2899 URL: https://issues.jboss.org/browse/TEIID-2899 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7 This is a regression from TEIID-2370. When pushing a limit below a join we need to check if there is a sideways correlation. Otherwise pushing to the left side may result in too few results. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2896) 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/TEIID-2896?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2896: ---------------------------------- Attachment: TEIID-2896.patch Here's a patch that uses a system property (org.teiid.bestEffortFixed) to control whether we make a best effort to return data from a fixed row that is too short or whether we throw an exception (the default). I don't think that we need this upstream based upon TEIID-2898. > Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2896 > URL: https://issues.jboss.org/browse/TEIID-2896 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Van Halbert > Attachments: TEIID-2896.patch > > > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2896) 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/TEIID-2896?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2896: ---------------------------------- Fix Version/s: (was: 8.7) > Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2896 > URL: https://issues.jboss.org/browse/TEIID-2896 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2898) Allow selector to be used with fixed width

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2898?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2898. ----------------------------------- Resolution: Done Relaxed the validation and updated the processing logic to allow for selectors with fixed width. > Allow selector to be used with fixed width > ------------------------------------------ > > Key: TEIID-2898 > URL: https://issues.jboss.org/browse/TEIID-2898 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7 > > > To allow for fixed width files containing multiple record types, the selector functionality should apply to fixed width as well. At least initially this will be restricted to only the overall selector as positional selector column references won't be possible. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2896) 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/TEIID-2896?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2896: ---------------------------------- Assignee: (was: Barry LaFond) With TEIID-2898, this issue does as written does not need to be exist upstream as the selector support is a better option. If supports wants one, I can provide a patch to allow this behavior for use with EDS. > Add TEXTTABLE function capabilities to interpret fixed width data file content that is shorter than the defined line length > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2896 > URL: https://issues.jboss.org/browse/TEIID-2896 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Van Halbert > Fix For: 8.7 > > > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2898) Allow selector to be used with fixed width

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2898?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2898: ---------------------------------- Description: To allow for fixed width files containing multiple record types, the selector functionality should apply to fixed width as well. At least initially this will be restricted to only the overall selector as positional selector column references won't be possible. (was: 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.) > Allow selector to be used with fixed width > ------------------------------------------ > > Key: TEIID-2898 > URL: https://issues.jboss.org/browse/TEIID-2898 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.7 > > > To allow for fixed width files containing multiple record types, the selector functionality should apply to fixed width as well. At least initially this will be restricted to only the overall selector as positional selector column references won't be possible. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2898) Allow selector to be used with fixed width

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2898?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2898: ---------------------------------- Assignee: Steven Hawkins (was: Barry LaFond) > Allow selector to be used with fixed width > ------------------------------------------ > > Key: TEIID-2898 > URL: https://issues.jboss.org/browse/TEIID-2898 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7 > > > To allow for fixed width files containing multiple record types, the selector functionality should apply to fixed width as well. At least initially this will be restricted to only the overall selector as positional selector column references won't be possible. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2898) Allow selector to be used with fixed width

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2898: ------------------------------------- Summary: Allow selector to be used with fixed width Key: TEIID-2898 URL: https://issues.jboss.org/browse/TEIID-2898 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Van Halbert Assignee: Barry LaFond Fix For: 8.7 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-965) Need Excel file importer / connector

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-965?page=com.atlassian.jira.plugin.... ] Ramesh Reddy reassigned TEIID-965: ---------------------------------- Assignee: Ramesh Reddy > Need Excel file importer / connector > ------------------------------------ > > Key: TEIID-965 > URL: https://issues.jboss.org/browse/TEIID-965 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: Open To Community > > > Really need to add an Excel connector in SP1. The easiest way to do this is probably with one of the open source JDBC drivers that work over Excel files. > Something like: > https://xlsql.dev.java.net/ - Excel JDBC driver (GPL unfortunately, so we probably can't distribute the driver) > http://www.andykhan.com/jexcelapi/ - Java Excel API (GPL too) > http://xlsjdbc.sourceforge.net/ - LGPL (uses Apache POI), really cheesy and maybe not being updated > http://jakarta.apache.org/poi/ - Excel API, event-based and not particularly friendly > http://www.vistaportal.com/products/vistajdbc-QA.htm - commercial -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-965) Need Excel file importer / connector

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-965?page=com.atlassian.jira.plugin.... ] Ramesh Reddy commented on TEIID-965: ------------------------------------ I will see if I can accomplish this using Apache POI, this seems to be always issue dealing with JDBC-ODBC bridge. > Need Excel file importer / connector > ------------------------------------ > > Key: TEIID-965 > URL: https://issues.jboss.org/browse/TEIID-965 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: Open To Community > > > Really need to add an Excel connector in SP1. The easiest way to do this is probably with one of the open source JDBC drivers that work over Excel files. > Something like: > https://xlsql.dev.java.net/ - Excel JDBC driver (GPL unfortunately, so we probably can't distribute the driver) > http://www.andykhan.com/jexcelapi/ - Java Excel API (GPL too) > http://xlsjdbc.sourceforge.net/ - LGPL (uses Apache POI), really cheesy and maybe not being updated > http://jakarta.apache.org/poi/ - Excel API, event-based and not particularly friendly > http://www.vistaportal.com/products/vistajdbc-QA.htm - commercial -- 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2014