September 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3148) Teiid exception with vdb from flat file containing utf8 non-ascii character

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-3148?page=com.atlassian.jira.plugin... ] Jan Stastny commented on TEIID-3148: ------------------------------------ In my model I use this query: SELECT * FROM (EXEC TextTeiid.getTextFiles('EmpData.txt')) AS f, TEXTTABLE(f.file COLUMNS lastName string, firstName string, middleName string, empId biginteger, department string, annualSalary double, title string, homePhone string, mgrId biginteger, street string, city string, state string, ZipCode string HEADER 3) AS emp > Teiid exception with vdb from flat file containing utf8 non-ascii character > --------------------------------------------------------------------------- > > Key: TEIID-3148 > URL: https://issues.jboss.org/browse/TEIID-3148 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: Windows OS > Reporter: Jan Stastny > Assignee: Steven Hawkins > > This issue is Windows OS specific. When trying to parse text csv file in utf8 which contains non-ascii characters an exception occurs. When the non-ascii characters are removed, everything passes well. On RHEL or Solaris this issue doesn't occur. > TEIID30020 Processing exception for request rgzZ3dn9tVMX.0 'TEIID30179 Text parse error: Could not read data in file:/w:/workspace/JDV6_1_BQT-jstastny/jdk/java17_default/label/Win2k8_x86/eap/standalone/deployments/TextEmployeeTest-files/EmpData.txt'. Originally TeiidProcessingException 'Input length = 1' CoderResult.java:278. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3148) Teiid exception with vdb from flat file containing utf8 non-ascii character

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3148?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3148: --------------------------------------- Are you telling Teiid the appropriate character set to use? Can you provide the details of how you supplying the text file to the texttable function? > Teiid exception with vdb from flat file containing utf8 non-ascii character > --------------------------------------------------------------------------- > > Key: TEIID-3148 > URL: https://issues.jboss.org/browse/TEIID-3148 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: Windows OS > Reporter: Jan Stastny > Assignee: Steven Hawkins > > This issue is Windows OS specific. When trying to parse text csv file in utf8 which contains non-ascii characters an exception occurs. When the non-ascii characters are removed, everything passes well. On RHEL or Solaris this issue doesn't occur. > TEIID30020 Processing exception for request rgzZ3dn9tVMX.0 'TEIID30179 Text parse error: Could not read data in file:/w:/workspace/JDV6_1_BQT-jstastny/jdk/java17_default/label/Win2k8_x86/eap/standalone/deployments/TextEmployeeTest-files/EmpData.txt'. Originally TeiidProcessingException 'Input length = 1' CoderResult.java:278. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3141) Bad result of query with GROUB BY clause (underlying sybase15 datasource)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3141?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3141: --------------------------------------- I wouldn't until required to by a customer issue as this should be a relatively uncommon query structure, it's a source issue, and there's no simplistic way to express to the engine when it will occur (for example it isn't sufficient to say that no functions are allowed in the group by as the functions are added due to implicit conversion logic in the translator). > Bad result of query with GROUB BY clause (underlying sybase15 datasource) > ------------------------------------------------------------------------- > > Key: TEIID-3141 > URL: https://issues.jboss.org/browse/TEIID-3141 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: sun 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Description: > There is sybase15 database with table named SmallA and table named SmallA in VDB which is mapped to sybase table (see tables definition below). > I am trying to run query against VDB: > SELECT > INTKEY, STRINGKEY, INTNUM, STRINGNUM, FLOATNUM, LONGNUM, DOUBLENUM, BYTENUM, DATEVALUE, TIMEVALUE, TIMESTAMPVALUE, BOOLEANVALUE, CHARVALUE, SHORTVALUE, BIGINTEGERVALUE, BIGDECIMALVALUE > FROM > BQT1.SMALLA > GROUP BY > INTKEY, STRINGKEY, INTNUM, STRINGNUM, FLOATNUM, LONGNUM, DOUBLENUM, BYTENUM, DATEVALUE, TIMEVALUE, TIMESTAMPVALUE, BOOLEANVALUE, CHARVALUE, SHORTVALUE, BIGINTEGERVALUE, BIGDECIMALVALUE > Result is table which misses some values (the other values are OK): > FloatNum: always 0 > ByteNum: always 0 > DateValue: always 1900-01-01 > TimeValue: always 00:00:00 > BooleanValue: always 'false' > CharValue: always empty character > ShortValue: always 0 > BigIntegerValue: always 0 > BigDecimalValue: always 0 > After removing 'INTKEY' and 'STRINGKEY' from the query is result OK (sybase15 has indices only for these two columns). > /////////////////// > Table definition > /////////////////// > SmallA (sybase) has these columns (name:type): > IntKey:int -> PRIMARY KEY, HAS INDEX > StringKey:varchar -> HAS INDEX > IntNum:int > StringNum:varchar > FloatNum:float > LongNum:numeric > DoubleNum:float > ByteNum:real > DateValue:datetime > TimeValue:datetime > TimestampValue:datetime > BooleanValue:tinyint > CharValue:char > ShortValue:numeric > BigIntegerValue:numeric > BigDecimalValue:numeric > ObjectValue:text > SmallA (VDB) has these columns (name:type): > IntKey:integer > StringKey:string > IntNum:integer > StringNum:string > FloatNum:float > LongNum:long > DoubleNum:double > ByteNum:byte > DateValue:date > TimeValue:time > TimestampValue:timestamp > BooleanValue:boolean > CharValue:char > ShortValue:short > BigIntegerValue:biginteger > BigDecimalValue:bigdecimal > ObjectValue:object -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3148) Teiid exception with vdb from flat file containing utf8 non-ascii character

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3148?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3148: ------------------------------------------- Bugzilla Update: (was: Perform) > Teiid exception with vdb from flat file containing utf8 non-ascii character > --------------------------------------------------------------------------- > > Key: TEIID-3148 > URL: https://issues.jboss.org/browse/TEIID-3148 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: Windows OS > Reporter: Jan Stastny > Assignee: Steven Hawkins > > This issue is Windows OS specific. When trying to parse text csv file in utf8 which contains non-ascii characters an exception occurs. When the non-ascii characters are removed, everything passes well. On RHEL or Solaris this issue doesn't occur. > TEIID30020 Processing exception for request rgzZ3dn9tVMX.0 'TEIID30179 Text parse error: Could not read data in file:/w:/workspace/JDV6_1_BQT-jstastny/jdk/java17_default/label/Win2k8_x86/eap/standalone/deployments/TextEmployeeTest-files/EmpData.txt'. Originally TeiidProcessingException 'Input length = 1' CoderResult.java:278. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3148) Teiid exception with vdb from flat file containing utf8 non-ascii character

by Jan Stastny (JIRA)

Jan Stastny created TEIID-3148: ---------------------------------- Summary: Teiid exception with vdb from flat file containing utf8 non-ascii character Key: TEIID-3148 URL: https://issues.jboss.org/browse/TEIID-3148 Project: Teiid Issue Type: Bug Affects Versions: 8.7.1 Environment: Windows OS Reporter: Jan Stastny Assignee: Steven Hawkins This issue is Windows OS specific. When trying to parse text csv file in utf8 which contains non-ascii characters an exception occurs. When the non-ascii characters are removed, everything passes well. On RHEL or Solaris this issue doesn't occur. TEIID30020 Processing exception for request rgzZ3dn9tVMX.0 'TEIID30179 Text parse error: Could not read data in file:/w:/workspace/JDV6_1_BQT-jstastny/jdk/java17_default/label/Win2k8_x86/eap/standalone/deployments/TextEmployeeTest-files/EmpData.txt'. Originally TeiidProcessingException 'Input length = 1' CoderResult.java:278. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3147) Add information about the amount of data (in bytes) returned by each query

by Joao Viragine (JIRA)

Joao Viragine created TEIID-3147: ------------------------------------ Summary: Add information about the amount of data (in bytes) returned by each query Key: TEIID-3147 URL: https://issues.jboss.org/browse/TEIID-3147 Project: Teiid Issue Type: Feature Request Reporter: Joao Viragine Assignee: Steven Hawkins It would be nice if we had the information about the amount of data (in bytes) returned by each query. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3141) Bad result of query with GROUB BY clause (underlying sybase15 datasource)

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3141?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-3141: ------------------------------------- OK. Can you roughly estimate when you will deal with this bug (1/2/3 month(s), ...)? > Bad result of query with GROUB BY clause (underlying sybase15 datasource) > ------------------------------------------------------------------------- > > Key: TEIID-3141 > URL: https://issues.jboss.org/browse/TEIID-3141 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: sun 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Description: > There is sybase15 database with table named SmallA and table named SmallA in VDB which is mapped to sybase table (see tables definition below). > I am trying to run query against VDB: > SELECT > INTKEY, STRINGKEY, INTNUM, STRINGNUM, FLOATNUM, LONGNUM, DOUBLENUM, BYTENUM, DATEVALUE, TIMEVALUE, TIMESTAMPVALUE, BOOLEANVALUE, CHARVALUE, SHORTVALUE, BIGINTEGERVALUE, BIGDECIMALVALUE > FROM > BQT1.SMALLA > GROUP BY > INTKEY, STRINGKEY, INTNUM, STRINGNUM, FLOATNUM, LONGNUM, DOUBLENUM, BYTENUM, DATEVALUE, TIMEVALUE, TIMESTAMPVALUE, BOOLEANVALUE, CHARVALUE, SHORTVALUE, BIGINTEGERVALUE, BIGDECIMALVALUE > Result is table which misses some values (the other values are OK): > FloatNum: always 0 > ByteNum: always 0 > DateValue: always 1900-01-01 > TimeValue: always 00:00:00 > BooleanValue: always 'false' > CharValue: always empty character > ShortValue: always 0 > BigIntegerValue: always 0 > BigDecimalValue: always 0 > After removing 'INTKEY' and 'STRINGKEY' from the query is result OK (sybase15 has indices only for these two columns). > /////////////////// > Table definition > /////////////////// > SmallA (sybase) has these columns (name:type): > IntKey:int -> PRIMARY KEY, HAS INDEX > StringKey:varchar -> HAS INDEX > IntNum:int > StringNum:varchar > FloatNum:float > LongNum:numeric > DoubleNum:float > ByteNum:real > DateValue:datetime > TimeValue:datetime > TimestampValue:datetime > BooleanValue:tinyint > CharValue:char > ShortValue:numeric > BigIntegerValue:numeric > BigDecimalValue:numeric > ObjectValue:text > SmallA (VDB) has these columns (name:type): > IntKey:integer > StringKey:string > IntNum:integer > StringNum:string > FloatNum:float > LongNum:long > DoubleNum:double > ByteNum:byte > DateValue:date > TimeValue:time > TimestampValue:timestamp > BooleanValue:boolean > CharValue:char > ShortValue:short > BigIntegerValue:biginteger > BigDecimalValue:bigdecimal > ObjectValue:object -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3141) Bad result of query with GROUB BY clause (underlying sybase15 datasource)

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3141?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-3141: ------------------------------------- I did not known about the issue with attachment, but my colleague already warned me. I will be carefull next time. > Bad result of query with GROUB BY clause (underlying sybase15 datasource) > ------------------------------------------------------------------------- > > Key: TEIID-3141 > URL: https://issues.jboss.org/browse/TEIID-3141 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: sun 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Description: > There is sybase15 database with table named SmallA and table named SmallA in VDB which is mapped to sybase table (see tables definition below). > I am trying to run query against VDB: > SELECT > INTKEY, STRINGKEY, INTNUM, STRINGNUM, FLOATNUM, LONGNUM, DOUBLENUM, BYTENUM, DATEVALUE, TIMEVALUE, TIMESTAMPVALUE, BOOLEANVALUE, CHARVALUE, SHORTVALUE, BIGINTEGERVALUE, BIGDECIMALVALUE > FROM > BQT1.SMALLA > GROUP BY > INTKEY, STRINGKEY, INTNUM, STRINGNUM, FLOATNUM, LONGNUM, DOUBLENUM, BYTENUM, DATEVALUE, TIMEVALUE, TIMESTAMPVALUE, BOOLEANVALUE, CHARVALUE, SHORTVALUE, BIGINTEGERVALUE, BIGDECIMALVALUE > Result is table which misses some values (the other values are OK): > FloatNum: always 0 > ByteNum: always 0 > DateValue: always 1900-01-01 > TimeValue: always 00:00:00 > BooleanValue: always 'false' > CharValue: always empty character > ShortValue: always 0 > BigIntegerValue: always 0 > BigDecimalValue: always 0 > After removing 'INTKEY' and 'STRINGKEY' from the query is result OK (sybase15 has indices only for these two columns). > /////////////////// > Table definition > /////////////////// > SmallA (sybase) has these columns (name:type): > IntKey:int -> PRIMARY KEY, HAS INDEX > StringKey:varchar -> HAS INDEX > IntNum:int > StringNum:varchar > FloatNum:float > LongNum:numeric > DoubleNum:float > ByteNum:real > DateValue:datetime > TimeValue:datetime > TimestampValue:datetime > BooleanValue:tinyint > CharValue:char > ShortValue:numeric > BigIntegerValue:numeric > BigDecimalValue:numeric > ObjectValue:text > SmallA (VDB) has these columns (name:type): > IntKey:integer > StringKey:string > IntNum:integer > StringNum:string > FloatNum:float > LongNum:long > DoubleNum:double > ByteNum:byte > DateValue:date > TimeValue:time > TimestampValue:timestamp > BooleanValue:boolean > CharValue:char > ShortValue:short > BigIntegerValue:biginteger > BigDecimalValue:bigdecimal > ObjectValue:object -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3146) Billing mechanism based on the query's complexity

by Joao Viragine (JIRA)

Joao Viragine created TEIID-3146: ------------------------------------ Summary: Billing mechanism based on the query's complexity Key: TEIID-3146 URL: https://issues.jboss.org/browse/TEIID-3146 Project: Teiid Issue Type: Feature Request Reporter: Joao Viragine Assignee: Steven Hawkins Priority: Minor It would be nice if we had a billing mechanism based on the query's complexity. Teeid exposes information about the queries issued, the amount of records returned, the time elapsed and the query plan. It could also expose the amount of data (in bytes) returned by each query. We could combine the above data plus the query complexity to create a score for a billing calculation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3137) Change infinispan-cache translator to support JDG 6 and no longer support pre 6.0 infinispan

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3137?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3137: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/330, https://github.com/teiid/teiid/pull/331 (was: https://github.com/teiid/teiid/pull/330) PR 330 is for master PR 331 is for 8.7.x branch > Change infinispan-cache translator to support JDG 6 and no longer support pre 6.0 infinispan > -------------------------------------------------------------------------------------------- > > Key: TEIID-3137 > URL: https://issues.jboss.org/browse/TEIID-3137 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Change the infinispan-cache translator to support JDG 6 using library mode. Also, remove support for infinispan v.5. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2014