October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3582) Add the query requestID to all lines for that query in the logs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3582?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3582: ---------------------------------- Fix Version/s: 8.12.2 (was: 8.12.1) > Add the query requestID to all lines for that query in the logs > --------------------------------------------------------------- > > Key: TEIID-3582 > URL: https://issues.jboss.org/browse/TEIID-3582 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Fix For: 8.12.2 > > > Currently when running a query, the logs show the requestId on most of the lines but not all, especially CONNECTOR. > for example, the following line doesn't have it: > 14:13:34,071 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue13) Source-specific command: .... > That's the problem. When lots of queries are running, user wants to grep through the log for that requestid and get just that one query's stuff. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3717) Enable SNI (Server Name Indication) support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3717?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3717: ---------------------------------- Fix Version/s: 8.12.2 (was: 8.12.1) > Enable SNI (Server Name Indication) support > ------------------------------------------- > > Key: TEIID-3717 > URL: https://issues.jboss.org/browse/TEIID-3717 > Project: Teiid > Issue Type: Feature Request > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.12.2 > > > Enable SNI support -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3750) Allow the parsing of an expression

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3750?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3750: ---------------------------------- Fix Version/s: 8.12.2 (was: 8.12.1) > Allow the parsing of an expression > ---------------------------------- > > Key: TEIID-3750 > URL: https://issues.jboss.org/browse/TEIID-3750 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12.2 > > > Now that we have an extension property, we could allow an expression to be used in parsing rather than just a string. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2729) Dynamic VDB xml requires sibling elements to be in a certain order

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2729?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2729: ---------------------------------- Fix Version/s: 8.12.2 (was: 8.12.1) > Dynamic VDB xml requires sibling elements to be in a certain order > ------------------------------------------------------------------ > > Key: TEIID-2729 > URL: https://issues.jboss.org/browse/TEIID-2729 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Affects Versions: 8.5 > Reporter: Mark Drilling > Fix For: 8.12.2 > > > In my *-vdb.xml, I have a model defined per following snippet: > <model name="myModel" type="PHYSICAL" visible="true"> > <source name="myModel" translator-name="hive" connection-jndi-name="Hive12Src" /> > <property name="trimColumnNames" value="true" /> > </model> > The vdb.xml failed to parse, so I moved the <property> element ahead of <source> and then it worked. > I don't think element ordering should matter in this case? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2884) Support for Amazon Elastic MapReduce

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2884?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2884: ---------------------------------- Fix Version/s: 8.12.x (was: 8.12.1) > Support for Amazon Elastic MapReduce > ------------------------------------ > > Key: TEIID-2884 > URL: https://issues.jboss.org/browse/TEIID-2884 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Kylin Soong > Fix For: 8.12.x > > > Amazon Elastic MapReduce > from http://en.wikipedia.org/wiki/Amazon_Elastic_MapReduce#Amazon_Elastic_MapR... > Elastic MapReduce (EMR)was introduced by Amazon in April 2009. Provisioning of the Hadoop cluster, running and terminating jobs, and handling data transfer between EC2 and S3 are automated by Elastic MapReduce. Apache Hive, which is built on top of Hadoop for providing data warehouse services, is also offered in Elastic MapReduce. > ... > In June 2012, premium options for EMR were added that replace ordinary Hadoop with MapR's M3 and M5 versions. These options provide additional capabilities over and above what the default EMR offering provides. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3789) Enable setting on SOLR translator for controlling timezone setting for Date and Timestamp columns

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3789?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3789: ---------------------------------- Fix Version/s: 8.12.x > Enable setting on SOLR translator for controlling timezone setting for Date and Timestamp columns > ------------------------------------------------------------------------------------------------- > > Key: TEIID-3789 > URL: https://issues.jboss.org/browse/TEIID-3789 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Fix For: 8.12.x > > > Timezone of DV server has influence on Date and Timestamp columns in some data sources -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3788) Enable setting on JDG translator for controlling timezone setting for Date and Timestamp columns

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3788?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3788: ---------------------------------- Fix Version/s: 8.12.x > Enable setting on JDG translator for controlling timezone setting for Date and Timestamp columns > ------------------------------------------------------------------------------------------------ > > Key: TEIID-3788 > URL: https://issues.jboss.org/browse/TEIID-3788 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Fix For: 8.12.x > > > Timezone of DV server has influence on Date and Timestamp columns in some data sources -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3231) Enable setting on MongoDB translator for controlling timezone setting for Date and Timestamp columns

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3231?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3231: ---------------------------------- Fix Version/s: 8.12.x > Enable setting on MongoDB translator for controlling timezone setting for Date and Timestamp columns > ---------------------------------------------------------------------------------------------------- > > Key: TEIID-3231 > URL: https://issues.jboss.org/browse/TEIID-3231 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Fix For: 8.12.x > > > Timezone of DV server has influence on Date and Timestamp columns in some data sources -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3554) Audit log is missing details related to what role was applied and what info was allowed or denied

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3554?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3554. ----------------------------------- Resolution: Incomplete Description Marking as incomplete description as we couldn't come to an understanding of what is needed. > Audit log is missing details related to what role was applied and what info was allowed or denied > ------------------------------------------------------------------------------------------------- > > Key: TEIID-3554 > URL: https://issues.jboss.org/browse/TEIID-3554 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: portfolioroles_data.xlsx > > > Using the dynamicvdb-dataroles quick start as the basis for triggering the audit log. Executing the view query: "Select * from StockPrice" . The query will only present the "price" column value when the user has the "prices" role. When performing queries with a user (name=teiidUser) that doesn't have the "prices" role versus one that does (name=portfolio), doesn't provide any discerning information in the audit log to indicate that a role was applied to the data. > Attaching excel file of the audit log data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3617) Provide an option to Limit per user based connections

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3617?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3617: ---------------------------------- Fix Version/s: 9.0 (was: 8.12.1) Moving to 9.0 where the consolidation of the session service makes this a little more feasible. > Provide an option to Limit per user based connections > ----------------------------------------------------- > > Key: TEIID-3617 > URL: https://issues.jboss.org/browse/TEIID-3617 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Xian Liu > Assignee: Steven Hawkins > Fix For: 9.0 > > > we deploy teiid for users to get data, but some users will create many connections to teiid and they are not necessary, I need to find a good way to limit each user account can only get like 50 connections or so -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2015