September 2014 - teiid-issues - Jboss List Archives

[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 commented on TEIID-3137: ------------------------------------ The commit does the following: - removes the connector-infinispan resource adapter, which was only supporting Infinispan 5 - upgraded translator-object from supporting Infinispan 5 to 6. The packaging changes, which will no longer include Infinispan 6 jar's in the kit, will be handled in TEIID-2700. > 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)

9 years, 7 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... ] Work on TEIID-3137 stopped by Van Halbert. ------------------------------------------ > 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: Van Halbert > > 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)

9 years, 7 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 > 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: Van Halbert > > 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)

9 years, 7 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: ------------------------------- Assignee: Steven Hawkins (was: Van Halbert) > 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3136) Possible threading issues with index metadata loading

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3136?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3136: --------------------------------- Fix Version/s: 8.4.4 > Possible threading issues with index metadata loading > ----------------------------------------------------- > > Key: TEIID-3136 > URL: https://issues.jboss.org/browse/TEIID-3136 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.4.4, 8.9 > > > Index metadata can be processed by several threads such that the modifications may not be seen appropriately by other threads. This could include the materialization table not being set appropriately and model not found errors. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3136) Possible threading issues with index metadata loading

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3136?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3136. ----------------------------------- Fix Version/s: 8.7.1 Resolution: Done Addressed by increasing the lock on the indexmetadata repository and by always resolving cross schema metadata. > Possible threading issues with index metadata loading > ----------------------------------------------------- > > Key: TEIID-3136 > URL: https://issues.jboss.org/browse/TEIID-3136 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > Index metadata can be processed by several threads such that the modifications may not be seen appropriately by other threads. This could include the materialization table not being set appropriately and model not found errors. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3073) Tableau Connection Issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3073?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3073: --------------------------------------- I don't really see much that we can do based upon the logs. The tableau folks would have to weigh in on what is the best approach to get support recognized and/or what additional SQL we should support to enable the queries they are trying to run. > Tableau Connection Issues > ------------------------- > > Key: TEIID-3073 > URL: https://issues.jboss.org/browse/TEIID-3073 > Project: Teiid > Issue Type: Bug > Components: ODBC, Server > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Attachments: server.log, server.log, tablue-wireshark.pcapng > > > It has been reported that using Tableu with Teiid ODBC port show the following errors. These need to be investigated and fixed > {code} > This ODBC driver does not support important capabilities used by Tableau. > This unsupported function is required for relative date filters: The date part named 'week' for the date function: DATETRUNC(date_part, date, [start_of_week]) > ----- > Tableau identified the following warnings for the ODBC data source named 'streamyx_sales (streamyx_sales.streamyx_sales) (TMJDV)': > This aggregation is unsupported: Attribute > This aggregation is unsupported: Std. Dev > This aggregation is unsupported: Std. Dev (Pop.) > This aggregation is unsupported: Trunc Week Number > This aggregation is unsupported: Variance > This aggregation is unsupported: Variance (Pop.) > This function is unsupported: % with parameter types 'integer, integer' > This function is unsupported: ABS(number) with parameter types 'float' > This function is unsupported: ABS(number) with parameter types 'integer' > This function is unsupported: ACOS(number) with parameter types 'float' > This function is unsupported: ASCII(string) with parameter types 'string' > This function is unsupported: ASIN(number) with parameter types 'float' > This function is unsupported: ATAN(number) with parameter types 'float' > This function is unsupported: ATAN2(y number, x number) with parameter types 'float, float' > This function is unsupported: CHAR(integer) with parameter types 'float' > This function is unsupported: CHAR(integer) with parameter types 'integer' > This function is unsupported: COS(angle) with parameter types 'float' > This function is unsupported: COT(angle) with parameter types 'float' > This function is unsupported: DATEPART_DAYOFWEEK_INTERNAL with parameter types 'date' > This function is unsupported: DATEPART_WEEK_INTERNAL with parameter types 'date' > This function is unsupported: DATETIME with parameter types 'integer' > This function is unsupported: DEGREES(number) with parameter types 'float' > This function is unsupported: EXP(number) with parameter types 'float' > This function is unsupported: LN with parameter types 'float' > This function is unsupported: LN(number) with parameter types 'float' > This function is unsupported: LOG with parameter types 'float' > This function is unsupported: LOG(number, [base]) with parameter types 'float' > This function is unsupported: PI() > This function is unsupported: POWER with parameter types 'float, integer' > This function is unsupported: POWER with parameter types 'integer, integer' > This function is unsupported: POWER(number,power) with parameter types 'float, integer' > This function is unsupported: POWER(number,power) with parameter types 'integer, integer' > This function is unsupported: RADIANS(number) with parameter types 'float' > This function is unsupported: ROUND(number, [decimals]) with parameter types 'float' > This function is unsupported: ROUND(number, [decimals]) with parameter types 'float, integer' > This function is unsupported: SIGN(number) with parameter types 'float' > This function is unsupported: SIN(angle) with parameter types 'float' > This function is unsupported: SPACE with parameter types 'float' > This function is unsupported: SPACE(number) with parameter types 'integer' > This function is unsupported: SQRT(number) with parameter types 'float' > This function is unsupported: SQUARE with parameter types 'float' > This function is unsupported: TAN(angle) with parameter types 'float' > This function is unsupported: The date part named 'week' for the date function: DATEDIFF(date_part, start_date, end_date, [start_of_week]) > This function is unsupported: The date part named 'week' for the date function: DATEDIFF(date_part, start_date, end_date, [start_of_week]) > This function is unsupported: The date part named 'week' for the date function: DATENAME(date_part, date, [start_of_week]) > This function is unsupported: The date part named 'week' for the date function: DATENAME(date_part, date, [start_of_week]) > This function is unsupported: The date part named 'week' for the date function: DATEPART(date_part, date, [start_of_week]) > This function is unsupported: The date part named 'week' for the date function: DATEPART(date_part, date, [start_of_week]) > This function is unsupported: The date part named 'weekday' for the date function: DATENAME(date_part, date, [start_of_week]) > This function is unsupported: The date part named 'weekday' for the date function: DATENAME(date_part, date, [start_of_week]) > This function is unsupported: The date part named 'weekday' for the date function: DATEPART(date_part, date, [start_of_week]) > This function is unsupported: The date part named 'weekday' for the date function: DATEPART(date_part, date, [start_of_week]) > This is unsupported: SELECT ... INTO > This is unsupported: Temporary tables > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3121) Teiid Standalone Server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3121?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3121: --------------------------------------- > For me bundling the libraries/frameworks seems ok, but bundling the whole platform seems not correct As Tom points out, other projects do offer monolithic downloads. But I do understand the concern about yet another download / maven artifact etc. > look like they are done in a Unix shell. Yes, but it is not a requirement. > I'm getting the feeling that what I'm asking for is in conflict with the productization done for JBoss DV Somewhat. Productization is a whole other thing, but no they would not what the usage of unmanaged dependencies. Maven ensures that artifacts we pull in are managed and that artifacts we produce are published (when nexus is working). > If that's the case then I totally understand and will back off. This boils down to 3 options: 1. Have a first class artifact produced by the maven build. 2. Have a second class artifact produced after the build. 3. Post install script(s) on the downloads page. I'm in favor of 1 and 3 or just having a development aid script. > 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)

9 years, 7 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 can't reproduce this locally. Can you provide a vdb and which sybase instance you are using? > 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)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3136) Possible threading issues with index metadata loading

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3136?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3136: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1146545 > Possible threading issues with index metadata loading > ----------------------------------------------------- > > Key: TEIID-3136 > URL: https://issues.jboss.org/browse/TEIID-3136 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > Index metadata can be processed by several threads such that the modifications may not be seen appropriately by other threads. This could include the materialization table not being set appropriately and model not found errors. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2014