March 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3350) Add system functions for EWKT & KML

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3350?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3350: --------------------------------------- The other difference I've seen for gml and kml is the inclusion of the srsName in GML. Is that something we should be doing? > Add system functions for EWKT & KML > ----------------------------------- > > Key: TEIID-3350 > URL: https://issues.jboss.org/browse/TEIID-3350 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Tom Arnold > Assignee: Steven Hawkins > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3206) EAP 6.3 - JDBC Datasources Test Connection

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3206?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3206: --------------------------------------- Should be addressed by TEIID-3371 > EAP 6.3 - JDBC Datasources Test Connection > ------------------------------------------ > > Key: TEIID-3206 > URL: https://issues.jboss.org/browse/TEIID-3206 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.9, 8.10 > Reporter: Tom Arnold > Assignee: Steven Hawkins > > Using `Test Connection` for JDBC Datasources seems to be broken in the standalone server built from 8.9.x and master. This is an issue with EAP 6.3 Alpha1. > This is reproducible with the built-in ExampleDS H2 database. Run the `install.sh`, unzip, add a management user (bin/add-user.sh), start the server, and then login to the admin console (localhost:9990). Then go to Profile -> Connector -> Data Sources -> ExampleDS -> Connection -> Test Connection. It will fail with this error: "JBAS010440: failed to invoke operation: JBAS010447: Connection is not valid. This also happens with Oracle and PostgreSQL datasources. > The datasources seem to work despite this, but it would be good to understand the root cause and get it fixed if possible. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3373) Add an org.teiid logging context in the config

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3373?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3373: ------------------------------- Issue Type: Enhancement (was: Quality Risk) > Add an org.teiid logging context in the config > ---------------------------------------------- > > Key: TEIID-3373 > URL: https://issues.jboss.org/browse/TEIID-3373 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Steven Hawkins > Assignee: Van Halbert > Fix For: 8.11 > > > It would be convenient to have an existing org.teiid entry in the logging config to allow admins to quickly enabled debug/trace logging. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3373) Add an org.teiid logging context in the config

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3373?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3373: --------------------------------------- It's probably not an attribute of a quality risk. Should standalone-teiid.xml be updated also? > Add an org.teiid logging context in the config > ---------------------------------------------- > > Key: TEIID-3373 > URL: https://issues.jboss.org/browse/TEIID-3373 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Reporter: Steven Hawkins > Assignee: Van Halbert > Fix For: 8.11 > > > It would be convenient to have an existing org.teiid entry in the logging config to allow admins to quickly enabled debug/trace logging. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3371) Upgrade Teiid with EAP 6.4 Alpha

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3371?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3371: ------------------------------------ Also, something that I need to do is clean up the transient dependencies so that the illegaltransitivereportonly property can be set to false. > Upgrade Teiid with EAP 6.4 Alpha > -------------------------------- > > Key: TEIID-3371 > URL: https://issues.jboss.org/browse/TEIID-3371 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.11 > Reporter: Van Halbert > Assignee: Ramesh Reddy > > Upgrade all the Teiid projects to be built based on EAP 6.4 Alpha. Currently, this would align with jboss-integration-platform-bom 6.0.0.CR25 and EAP Alpha version 7.5.0.Final-redhat-17. Note, 7.5.0.Final-redhat-17 is the version in the EAP kit, but only CR25 bom is available. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3368) The database-service.jar needs version version in its name

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3368?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3368: ------------------------------- Git Pull Request: https://github.com/teiid/teiid-extensions/pull/22 (was: https://github.com/vhalbert/teiid-extensions/commit/90e2b9d144f3b967ce81d...) > The database-service.jar needs version version in its name > ---------------------------------------------------------- > > Key: TEIID-3368 > URL: https://issues.jboss.org/browse/TEIID-3368 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 8.7.1, 8.11 > Reporter: Van Halbert > Assignee: Van Halbert > > The database-service.jar in the tepid-extensions needs to be built with a version in the name. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3373) Add an org.teiid logging context in the config

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3373?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3373: ------------------------------------ PR: https://github.com/teiid/teiid/pull/419 Did the PR attribute get removed and is no longer available? > Add an org.teiid logging context in the config > ---------------------------------------------- > > Key: TEIID-3373 > URL: https://issues.jboss.org/browse/TEIID-3373 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Reporter: Steven Hawkins > Assignee: Van Halbert > Fix For: 8.11 > > > It would be convenient to have an existing org.teiid entry in the logging config to allow admins to quickly enabled debug/trace logging. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3373) Add an org.teiid logging context in the config

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3373: ------------------------------------- Summary: Add an org.teiid logging context in the config Key: TEIID-3373 URL: https://issues.jboss.org/browse/TEIID-3373 Project: Teiid Issue Type: Quality Risk Components: Server Reporter: Steven Hawkins Assignee: Van Halbert Fix For: 8.11 It would be convenient to have an existing org.teiid entry in the logging config to allow admins to quickly enabled debug/trace logging. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3372) Support multiple metadata tags

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3372: ------------------------------------- Summary: Support multiple metadata tags Key: TEIID-3372 URL: https://issues.jboss.org/browse/TEIID-3372 Project: Teiid Issue Type: Feature Request Components: Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.11 To allow for a more flexible configuration, we should support multiple metadata tags under a model, rather than relying on comma separated values. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3369) Add a extension point to manipulate incoming sql

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3369?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3369: ---------------------------------- Fix Version/s: 8.11 > Add a extension point to manipulate incoming sql > ------------------------------------------------ > > Key: TEIID-3369 > URL: https://issues.jboss.org/browse/TEIID-3369 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > We should look at adding a client or server extension point for manipulating sql - just the sql string, pre resolving. This will allow more flexibility in dealing with clients that don't send queries directly understood by Teiid. For example a select for update. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2015