March 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3836) Create a quick start to demonstrate OData

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3836?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-3836 at 3/7/17 7:28 PM: ------------------------------------------------------------- I think there is NO need for this, you can take any example we should be able to do odata. We can close this IMO. We can add to show odata URL to console when VDB is deployed if that makes sense. was (Author: rareddy): I think there is need for this, you can take any example we should be able to do odata. We can close this IMO. We can add to show odata URL to console when VDB is deployed if that makes sense. > Create a quick start to demonstrate OData > ----------------------------------------- > > Key: TEIID-3836 > URL: https://issues.jboss.org/browse/TEIID-3836 > Project: Teiid > Issue Type: Task > Components: Quick Starts > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Van Halbert > Fix For: 9.3 > > > Add a quick start to demonstrate OData api may helpful for users. > After deploy portfolio-vdb.xml successful, I test with(http://localhost:8080/odata/Portfolio.1/Stocks.StockPrices) return a error: > {code} > TEIID16011 EntitySet "Stocks.StockPrices" is not found; Check the spelling, use modelName.tableName; The table that representing the Entity type must either have a PRIMARY KEY or UNIQUE key(s) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3836) Create a quick start to demonstrate OData

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3836?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3836: ------------------------------------- I think there is need for this, you can take any example we should be able to do odata. We can close this IMO. We can add to show odata URL to console when VDB is deployed if that makes sense. > Create a quick start to demonstrate OData > ----------------------------------------- > > Key: TEIID-3836 > URL: https://issues.jboss.org/browse/TEIID-3836 > Project: Teiid > Issue Type: Task > Components: Quick Starts > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Van Halbert > Fix For: 9.3 > > > Add a quick start to demonstrate OData api may helpful for users. > After deploy portfolio-vdb.xml successful, I test with(http://localhost:8080/odata/Portfolio.1/Stocks.StockPrices) return a error: > {code} > TEIID16011 EntitySet "Stocks.StockPrices" is not found; Check the spelling, use modelName.tableName; The table that representing the Entity type must either have a PRIMARY KEY or UNIQUE key(s) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4799) Accessing a JDBC source via ODATA creates stack trace in log

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4799?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4799: ------------------------------- Attachment: stacktrace.txt > Accessing a JDBC source via ODATA creates stack trace in log > ------------------------------------------------------------- > > Key: TEIID-4799 > URL: https://issues.jboss.org/browse/TEIID-4799 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.8.6_3 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: stacktrace.txt > > > When doing a get to a odata endpoint that will use a jdbc connection in data virtualization, there will be a transaction related stacktrace in the logs. This does not seem to create a problem but is confusing. > Version-Release number of selected component (if applicable): > 8.12.x > How reproducible: > Steps to Reproduce: > 1. Add a JDBC datasource model in the Teiid Design Perspective > 2. Add a Teiid Metadata view model using the JDBC source model > 3. Deploy the view model in a VDB > 4. Access the view model via an odata call -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4799) Accessing a JDBC source via ODATA creates stack trace in log

by Van Halbert (JIRA)

Van Halbert created TEIID-4799: ---------------------------------- Summary: Accessing a JDBC source via ODATA creates stack trace in log Key: TEIID-4799 URL: https://issues.jboss.org/browse/TEIID-4799 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 8.12.8.6_3 Reporter: Van Halbert Assignee: Steven Hawkins When doing a get to a odata endpoint that will use a jdbc connection in data virtualization, there will be a transaction related stacktrace in the logs. This does not seem to create a problem but is confusing. Version-Release number of selected component (if applicable): 8.12.x How reproducible: Steps to Reproduce: 1. Add a JDBC datasource model in the Teiid Design Perspective 2. Add a Teiid Metadata view model using the JDBC source model 3. Deploy the view model in a VDB 4. Access the view model via an odata call -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4709) Enable JDG resource adapter to pass the username/password to HotRod Client

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4709?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4709: ------------------------------------ PR for documentation: https://github.com/teiid/teiid-documents/pull/106 > Enable JDG resource adapter to pass the username/password to HotRod Client > -------------------------------------------------------------------------- > > Key: TEIID-4709 > URL: https://issues.jboss.org/browse/TEIID-4709 > Project: Teiid > Issue Type: Feature Request > Components: JDG Connector > Affects Versions: 9.3 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.3, 8.12.9.6_3 > > > Enable the JDG resource adapter to pass the username/password to the JDG hot rod client. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4636) In the SWARM readme's, need to indicate the URL to connect

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4636?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4636: ---------------------------------- Fix Version/s: 9.3.1 (was: 9.3) > In the SWARM readme's, need to indicate the URL to connect > ---------------------------------------------------------- > > Key: TEIID-4636 > URL: https://issues.jboss.org/browse/TEIID-4636 > Project: Teiid > Issue Type: Enhancement > Components: Quick Starts > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 9.3.1 > > > The quickstarts needs to include the information (i.e, URL, username, password, etc.) needed to connect to the swarm example. > Per Kylin: > By default 0.0.0.0 be bound as IP, 31000 as port. To bind a specific IP use system properties > --- > -Dswarm.bind.address=127.0.0.1 > --- > Some Fractions use a system properties to change the port number, but teiid not support it at moment. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4695) Provide a better error with an invalid skipToken

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4695?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4695: ---------------------------------- Fix Version/s: 9.3.1 9.3.1 (was: 9.3) > Provide a better error with an invalid skipToken > ------------------------------------------------ > > Key: TEIID-4695 > URL: https://issues.jboss.org/browse/TEIID-4695 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Kylin Soong > Priority: Optional > Fix For: 9.3.1 > > > The error message from an invalid skipToken could be improved - however users should not manually enter skipTokens. Similar errors still occur with our OData4 as the StringTokenizer used for the token will hit a no such element exception. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4315) HBase Quickstart issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4315?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4315: ---------------------------------- Fix Version/s: 9.3.1 9.3.1 (was: 9.3) > HBase Quickstart issues > ----------------------- > > Key: TEIID-4315 > URL: https://issues.jboss.org/browse/TEIID-4315 > Project: Teiid > Issue Type: Bug > Components: Quick Starts > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 9.3.1 > > > remove.cli script does not work. You need to remove items in revers order. You cannot remove driver if some data source is still using it. Please update remove.cli script: > From: > > module remove --name=org.apache.phoenix > > /subsystem=datasources/jdbc-driver=phoenix:remove() > > /subsystem=datasources/data-source=QSPhoenixDS:remove() > To: > > /subsystem=datasources/data-source=QSPhoenixDS:remove() > > /subsystem=datasources/jdbc-driver=phoenix:remove() > > module remove --name=org.apache.phoenix > ------- > As far as I know, option 'enabled=true' of 'add' operation for data-source is deprecated in CLI. Moreover, user needs to reload server to be able to use create data source. Please, update the script like follows: > From: > > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,enabled=true,use-java-context=true) > To: > > /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,use-java-context=true) > > /subsystem=datasources/data-source=QSPhoenixDS:enable > ------ > Files: hbase-as-a-datasource/README.md, hbase-as-a-datasource/src/scripts/setup.cli > Line: 57 - 3) Setup Phoenix Data Source > 1 - --resources=phoenix-4.2.1-client.jar > Please add an instruction to update phoenix version in setup.cli script if user uses different version of phoenix/hbase. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3683) Enhance the formula for caculating core size

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3683?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3683: ---------------------------------- Fix Version/s: 9.3.1 9.3.1 (was: 9.3) > Enhance the formula for caculating core size > -------------------------------------------- > > Key: TEIID-3683 > URL: https://issues.jboss.org/browse/TEIID-3683 > Project: Teiid > Issue Type: Enhancement > Components: Sizing Application > Reporter: Kylin Soong > Assignee: Kylin Soong > Priority: Minor > Fix For: 9.3.1 > > Attachments: sizing-tools-cores.png > > > I think we can consider to enhance in the following aspects: > 1. Q7 is hard for user to input > Q7 need some pre-test or run sample query via POC, this not easy for user to input, also they may feels confused. > 2. How to caculate core size? > Current we consider through serialize/deserialize， the linear serialize/deserialize percentage get from trial in my local pc, this may need more test/review. > 3. Whether we can use runnable app replace Web UI > If use runnable app like AdminShell, most of questions in attached png can cacualate and get a precise input, > Any idea/advice for this? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4796) Support automatic pushdown of unsupported functions in JDBC connectors.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4796?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4796. ----------------------------------- Resolution: Won't Fix The workaround to add a source function should be used for now. In this specific case oracle does not advertise the system functions in the databasemetadata, so that's not of help here. > Support automatic pushdown of unsupported functions in JDBC connectors. > ----------------------------------------------------------------------- > > Key: TEIID-4796 > URL: https://issues.jboss.org/browse/TEIID-4796 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 9.1.3 > Reporter: John Rodrigues > Assignee: Steven Hawkins > > Please refer to this discussion for context: https://developer.jboss.org/message/969432 > It would be nice if Teiid could support automatic pushdown of unsupported functions for JDBC connectors. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 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 2017