[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:
---------------------------------------
Presumably the query is fully pushed down either way correct?
> 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, 3 months
[JBoss JIRA] (TEIID-3141) Bad result of query with GROUB BY clause (underlying sybase15 datasource)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3141?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3141:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1146501
> 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, 3 months
[JBoss JIRA] (TEIID-3141) Bad result of query with GROUB BY clause (underlying sybase15 datasource)
by Juraj Duráni (JIRA)
Juraj Duráni created TEIID-3141:
-----------------------------------
Summary: 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, 3 months
[JBoss JIRA] (TEIID-3134) Impala sorting Issue
by Filip Nguyen (JIRA)
[ https://issues.jboss.org/browse/TEIID-3134?page=com.atlassian.jira.plugin... ]
Filip Nguyen commented on TEIID-3134:
-------------------------------------
It seems to be problem only on String columns. I tried timestamp, char, int and all sort the same as e.g. postgre translator
> Impala sorting Issue
> --------------------
>
> Key: TEIID-3134
> URL: https://issues.jboss.org/browse/TEIID-3134
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Van Halbert
>
> String sorting of impala is inconsistent with our expectations:
> Impala sorting
> ---------------------------
> SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA
> Results
> 1: -1
> 2: -10
> 3: -11
> 4: -12
> 5: -13
> 6: -14
> 7: -15
> 8: -16
> 9: -17
> 10: -18
> 11: -19
> 12: -2
> 13: -20
> 14: -21
> 15: -22
> 16: -24
> 17: -3
> 18: -4
> 19: -5
> 20: -6
> 21: -8
> 22: -9
> 23: 0
> 24: 1
> 25: 10
> 26: 11
> 27: 12
> 28: 13
> 29: 14
> 30: 15
> 31: 16
> 32: 17
> 33: 18
> 34: 19
> 35: 2
> 36: 20
> 37: 21
> 38: 22
> 39: 23
> 40: 24
> 41: 3
> 42: 4
> 43: 5
> 44: 6
> 45: 7
> 46: 8
> 47: null
> 48: null
> 49: null
> 50: null
> Expected
> ---------------------------
> While we expect sorting to be consistent with other sources:
> 1: 0
> 2: 1
> 3: -1
> 4: 10
> 5: -10
> 6: 11
> 7: -11
> 8: 12
> 9: -12
> 10: 13
> 11: -13
> 12: 14
> 13: -14
> 14: 15
> 15: -15
> 16: 16
> 17: -16
> 18: 17
> 19: -17
> 20: 18
> 21: -18
> 22: 19
> 23: -19
> 24: 2
> 25: -2
> 26: 20
> 27: -20
> 28: 21
> 29: -21
> 30: 22
> 31: -22
> 32: 23
> 33: 24
> 34: -24
> 35: 3
> 36: -3
> 37: 4
> 38: -4
> 39: 5
> 40: -5
> 41: 6
> 42: -6
> 43: 7
> 44: 8
> 45: -8
> 46: -9
> 47: null
> 48: null
> 49: null
> 50: null
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (TEIID-3121) Teiid Standalone Server
by Tom Arnold (JIRA)
[ https://issues.jboss.org/browse/TEIID-3121?page=com.atlassian.jira.plugin... ]
Tom Arnold commented on TEIID-3121:
-----------------------------------
Maven might be cleaner, but I wasn't sure where to start.
The steps in the release procedure (https://developer.jboss.org/wiki/TeiidReleaseProcedure) look like they are done in a Unix shell. The download URLs would need to be maintained in the script, but how often do they change? I think the only one that has changed recently is the Teiid Web Console URL.
I was thinking that "install.sh" would be run sometime after the Maven build. I'm not too familiar with the maven release plugin, so maybe there would be an extra step of checking out the tag so that the correct version is used (Final instead of Beta).
I'm getting the feeling that what I'm asking for is in conflict with the productization done for JBoss DV. If that's the case then I totally understand and will back off.
> Teiid Standalone Server
> -----------------------
>
> Key: TEIID-3121
> URL: https://issues.jboss.org/browse/TEIID-3121
> Project: Teiid
> Issue Type: Feature Request
> Components: Build/Kits
> Reporter: Tom Arnold
> Fix For: Open To Community
>
>
> Perform the server installation steps as part of the build and add the result to the downloads page. It seems like this is something that everyone who isn't using the embedded kit has to do anyways, and would hopefully eliminate confusion caused by people trying to deploy the runtime in unsupported versions of JBoss.
> * Teiid Runtime
> * Teiid Web Console
> * JBoss EAP 6.1 Alpha
> * Resteasy JAX-RS Patch
> End result would simplify the installation process to:
> 1. Unzip Teiid server.
> 2. Run `bin/add-user.sh` script.
> 3. Deploy custom translators, VDB, etc.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (TEIID-3140) Add getVDBType() method to the VDB interface
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3140?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3140:
---------------------------------------
Is it sufficient to just add the isXmlDeployment method?
> Add getVDBType() method to the VDB interface
> --------------------------------------------
>
> Key: TEIID-3140
> URL: https://issues.jboss.org/browse/TEIID-3140
> Project: Teiid
> Issue Type: Enhancement
> Reporter: Barry LaFond
> Assignee: Steven Hawkins
>
> Because Teiid supports mutliple VDB types, any tooling designed to interact (edit, deploy, undeploy, display etc...) with the runtime VDBs will need to be able to easilly distinguish what each VDB type is.
> Currently Teiid Designer utilizes PREVIEW and defeault VDBs with *vdb* file extensions and there are 2 types of dynamic VDBs, *xml* and *zip* files backed by DDL model metadata definitions.
> The current VDB interface currently doesn't provide a type.
> Request adding something like:
> {code}
> public enum VDBType {DEFAULT, PREVIEW, XML, DDL}
> /**
> * @return the vdb type
> */
> public VDBType getVDBType();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (TEIID-3125) Netezza translator - add support for the LIKE_REGEX predicate.
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3125?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3125.
-----------------------------------
Resolution: Done
Added support for just like_regex. Did not address the other functions for now.
> Netezza translator - add support for the LIKE_REGEX predicate.
> --------------------------------------------------------------
>
> Key: TEIID-3125
> URL: https://issues.jboss.org/browse/TEIID-3125
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> With version 6 of Jboss DV the Netezza translator doesn't support the LIKE_REGEX predicate.
> Netezza doesn't support regular expression by default, but with the installation of SQL Extensions toolkit this functionality is added. After installation Netezza provide the regular expression functions:
> regexp_extract()
> regexp_extract_all()
> regexp_extract_all_sp()
> regexp_extract_sp()
> regexp_instr()
> regexp_like()
> regexp_match_count()
> regexp_replace()
> regexp_replace_sp()
> IBM Netezza SQL Extensions toolkit is an optional package for IBM Netezza data warehouse appliances.
> After installing this toolkit on Netezza and requires that regular expression in JBoss DV syntax are pushed down (delegated) to Netezza to prevent that filtering in the Jboss DV server most be done.
> So please provide a configurable option in the Netezza translator of Jboss DV by which we can enable the LIKE_REGEX predicate for Netezza. This option when enabled will assume that the Netezza SQL extension toolkit is installed and the function regexp_like() is available.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (TEIID-3011) rewrite skipped
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3011?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3011:
------------------------------------------------
jolee(a)redhat.com changed the Status of [bug 1110409|https://bugzilla.redhat.com/show_bug.cgi?id=1110409] from MODIFIED to CLOSED
> rewrite skipped
> ---------------
>
> Key: TEIID-3011
> URL: https://issues.jboss.org/browse/TEIID-3011
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7, 8.4.3, 8.7.1
>
>
> The rewrite of a set predicate is being bypassed when all of the in values are constants, but when pushed through a view with a convert on the left expression there is still optimizations that can be performed.
> For example:
> select * from (select e1, e2 from pm1.g1 union all select convert(e2, string), e2 from pm1.g2) x where e1 in ('1', '2')
> such that e1 is string and e2 is integer, we expect that the second branch will have criteria of the form "e2 in (1, 2)" - with no conversion.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months