June 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3845) select count(*) query not working on SimpleDB connector in Teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3845?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3845. --------------------------------- > select count(*) query not working on SimpleDB connector in Teiid > ---------------------------------------------------------------- > > Key: TEIID-3845 > URL: https://issues.jboss.org/browse/TEIID-3845 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.9 > Reporter: Pranav K > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.12.3, 8.13 > > > select count(*) query not working on SimpleDB connector -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3682) Add logon properties to audit messages

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3682?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3682. --------------------------------- > Add logon properties to audit messages > -------------------------------------- > > Key: TEIID-3682 > URL: https://issues.jboss.org/browse/TEIID-3682 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12.3, 8.13 > > > We expanded logon information in 8.12, but did not yet include all logon properties, which can include the client ip address - but there are limitations since the client ip and related fields would only be set for JDBC connections and not yet for local usage through ODBC/web. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3914) Datetime values not properly encoded in OData4 entity identifiers

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3914?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3914. --------------------------------- > Datetime values not properly encoded in OData4 entity identifiers > ----------------------------------------------------------------- > > Key: TEIID-3914 > URL: https://issues.jboss.org/browse/TEIID-3914 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12.4 > Reporter: Simon Evenepoel > Assignee: Ramesh Reddy > Labels: odata, > Fix For: 8.13, 9.0, 8.12.5 > > Attachments: TEIID-3914.diff > > > When the primary key of an OData entry consists of a timestamp or datetime value an odata get request returns the following error message: > java.net.URISyntaxException: Illegal character in scheme name at index n: tablename(partofkey='keyvalue',datepartofkey=2016-01-13 11:25:03.884) > For more information visit this thread on the user forums in which [~shawkins] said: > _"Actually there is an issue with our handling of building the entity id to go into the response. We are not properly encoding datatime values.''_ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3896) When error occurs in the materialization process, an ERROR should be logged instead of DEBUG

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3896?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3896. --------------------------------- > When error occurs in the materialization process, an ERROR should be logged instead of DEBUG > -------------------------------------------------------------------------------------------- > > Key: TEIID-3896 > URL: https://issues.jboss.org/browse/TEIID-3896 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.12.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.13, 8.12.4 > > > When trying to do materialization, there's an issue (DEBUG) appearing in the server.log: > 09:58:51,272 DEBUG [org.teiid.PROCESSOR] (Worker5_QueryProcessorQueue302) org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due to: Group specified is ambiguous, resubmit the query by fully qualifying the group name: Stock > I believe this be logged as an ERROR as it appears to be detrimental to what's being materialized. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2973) OData 4 support with Olingo

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2973?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2973. --------------------------------- > OData 4 support with Olingo > --------------------------- > > Key: TEIID-2973 > URL: https://issues.jboss.org/browse/TEIID-2973 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors, OData > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.11 > > > Whenever an olingo final is available for odata 3/4 we'll want to utilize that. The best guess now is that this will happen in the 8.9 timeframe. Additional support can then be added for later odata features, which will have subtasks as necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4247) OData - support date and time functions

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4247?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-4247: ----------------------------------- Assignee: Ramesh Reddy > OData - support date and time functions > --------------------------------------- > > Key: TEIID-4247 > URL: https://issues.jboss.org/browse/TEIID-4247 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > Fix For: 9.1 > > > The functions date() and time() are currently not supported in odata queries, e.g. running query {noformat}http://localhost:8080/odata4/olingo_basic/Source/SimpleDataTable?$filter=timeval%20gt%20time(now()){noformat} > returns {code:xml} > <?xml version='1.0' encoding='UTF-8'?> > <error xmlns="http://docs.oasis-open.org/odata/ns/metadata"> > <code>TEIID16027</code> > <message>TEIID16027 Function time is not currently supported </message> > </error> > {code} > This is allowed behaviour per the [odata spec|http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/par...], but it would be good to have these functions implemented. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4247) OData - support date and time functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4247?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4247: ------------------------------------- Fix Version/s: 9.1 Assignee: (was: Steven Hawkins) > OData - support date and time functions > --------------------------------------- > > Key: TEIID-4247 > URL: https://issues.jboss.org/browse/TEIID-4247 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Fix For: 9.1 > > > The functions date() and time() are currently not supported in odata queries, e.g. running query {noformat}http://localhost:8080/odata4/olingo_basic/Source/SimpleDataTable?$filter=timeval%20gt%20time(now()){noformat} > returns {code:xml} > <?xml version='1.0' encoding='UTF-8'?> > <error xmlns="http://docs.oasis-open.org/odata/ns/metadata"> > <code>TEIID16027</code> > <message>TEIID16027 Function time is not currently supported </message> > </error> > {code} > This is allowed behaviour per the [odata spec|http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/par...], but it would be good to have these functions implemented. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4250) Add translator to support Google Cloud Bigtable

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4250?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4250: ------------------------------------- Fix Version/s: Open To Community Assignee: (was: Steven Hawkins) > Add translator to support Google Cloud Bigtable > ------------------------------------------------ > > Key: TEIID-4250 > URL: https://issues.jboss.org/browse/TEIID-4250 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Fix For: Open To Community > > > Add translator to support Google Cloud Bigtable -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4155) Explore the possibility to use JBeret as materialization schedular

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4155?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4155: -------------------------------- Parent: TEIID-4249 Issue Type: Sub-task (was: Enhancement) > Explore the possibility to use JBeret as materialization schedular > ------------------------------------------------------------------ > > Key: TEIID-4155 > URL: https://issues.jboss.org/browse/TEIID-4155 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > > Right now the managed external materialization uses the our own very basic job scheduler, it would be nice if we can use JBeret batch processing system to automatically create jobs based on the materialization extension properties. > JBeret is JSR-352, looks simple enough to integrate. The advantages for us would be > - a standard scheduler, which will also work in "embedded" as this supposed to work in Java SE > - Gives CLI based management > - may be better metrics on time taken and error management -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-4251: ----------------------------------- Summary: Built in support for Postgres DB as materialization target Key: TEIID-4251 URL: https://issues.jboss.org/browse/TEIID-4251 Project: Teiid Issue Type: Sub-task Components: Server Reporter: Ramesh Reddy If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like - Creation of a common STATUS table - Creation of the materilization targets (create views on dbms) - On load, on undeploy and load scripts for all the materialization views We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2016