June 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5957) enable EXTRACT DOW/DOY from timestamp

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5957?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5957. ----------------------------------- Resolution: Done Added and documented DOW and DOY as extract targets. > enable EXTRACT DOW/DOY from timestamp > ------------------------------------- > > Key: TEIID-5957 > URL: https://issues.redhat.com/browse/TEIID-5957 > Project: Teiid > Issue Type: Enhancement > Components: Grammar > Affects Versions: 13.1 > Reporter: Ken Geis > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Similar to TEIID-5896, I would like Teiid to support > {code:sql} > EXTRACT(DOW FROM ...) > {code} > and > {code:sql} > EXTRACT(DOY FROM ...) > {code} > for Tableau compatibility. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5957) enable EXTRACT DOW/DOY from timestamp

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5957?focusedWorklogId=12451209&pag... ] Steven Hawkins logged work on TEIID-5957: ----------------------------------------- Author: Steven Hawkins Created on: 02/Jun/20 10:30 PM Start Date: 02/Jun/20 10:30 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 2 hours) Time Spent: 2 hours Worklog Id: (was: 12451209) > enable EXTRACT DOW/DOY from timestamp > ------------------------------------- > > Key: TEIID-5957 > URL: https://issues.redhat.com/browse/TEIID-5957 > Project: Teiid > Issue Type: Enhancement > Components: Grammar > Affects Versions: 13.1 > Reporter: Ken Geis > Assignee: Steven Hawkins > Priority: Major > Fix For: 15.0 > > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Similar to TEIID-5896, I would like Teiid to support > {code:sql} > EXTRACT(DOW FROM ...) > {code} > and > {code:sql} > EXTRACT(DOY FROM ...) > {code} > for Tableau compatibility. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-206) Create native connector to interact with HDFS as a datasource

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-206?page=com.atlassian.jira.plug... ] Steven Hawkins reassigned TEIIDSB-206: -------------------------------------- Assignee: Aditya Manglam Sharma > Create native connector to interact with HDFS as a datasource > ------------------------------------------------------------- > > Key: TEIIDSB-206 > URL: https://issues.redhat.com/browse/TEIIDSB-206 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Van Halbert > Assignee: Aditya Manglam Sharma > Priority: Major > Fix For: 1.6.0 > > > Would like to have native connector > To interact with HDFS as a datasource from a DV perspective there are at least two options: > 1 - HttpFS > 2 - WebHDFS > Both options seems to be in practise very slow. I heard 2x slower. > It would be nice if we can create a native HDFS connector. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-206) Create native connector to interact with HDFS as a datasource

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-206?page=com.atlassian.jira.plug... ] Steven Hawkins moved TEIID-5966 to TEIIDSB-206: ----------------------------------------------- Project: Teiid Spring Boot (was: Teiid) Key: TEIIDSB-206 (was: TEIID-5966) Component/s: datasource (was: Misc. Connectors) Fix Version/s: 1.6.0 (was: Backlog) > Create native connector to interact with HDFS as a datasource > ------------------------------------------------------------- > > Key: TEIIDSB-206 > URL: https://issues.redhat.com/browse/TEIIDSB-206 > Project: Teiid Spring Boot > Issue Type: Feature Request > Components: datasource > Reporter: Van Halbert > Priority: Major > Fix For: 1.6.0 > > > Would like to have native connector > To interact with HDFS as a datasource from a DV perspective there are at least two options: > 1 - HttpFS > 2 - WebHDFS > Both options seems to be in practise very slow. I heard 2x slower. > It would be nice if we can create a native HDFS connector. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5966) Create native connector to interact with HDFS as a datasource

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5966: ------------------------------------- Summary: Create native connector to interact with HDFS as a datasource Key: TEIID-5966 URL: https://issues.redhat.com/browse/TEIID-5966 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Reporter: Van Halbert Fix For: Backlog Would like to have native connector To interact with HDFS as a datasource from a DV perspective there are at least two options: 1 - HttpFS 2 - WebHDFS Both options seems to be in practise very slow. I heard 2x slower. It would be nice if we can create a native HDFS connector. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5963) Teiid imported all schemas from PG

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5963?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5963: --------------------------------------- > JDBC driver made a SELECT to DB when retrieve data of every type? Yes the pg driver loads several fields per type: https://github.com/pgjdbc/pgjdbc/blob/0eb5eea99d46e49c92b24776a9cd782b7fa... Initial query: https://github.com/pgjdbc/pgjdbc/blob/0eb5eea99d46e49c92b24776a9cd782b7fa... Type info loaded per type: https://github.com/pgjdbc/pgjdbc/blob/49d66e4ec0c514fbfa78cd72f7a8aeb7424... > Teiid imported all schemas from PG > ---------------------------------- > > Key: TEIID-5963 > URL: https://issues.redhat.com/browse/TEIID-5963 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 14.0 > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > When we started teiid spring boot app, we have long start time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5963) Teiid imported all schemas from PG

by Renat Eskenin (Jira)

[ https://issues.redhat.com/browse/TEIID-5963?page=com.atlassian.jira.plugi... ] Renat Eskenin commented on TEIID-5963: -------------------------------------- We have 15min for start service. It is problem :) How about this message in log <=BE CommandStatus(SELECT 1) JDBC driver made a SELECT to DB when retrieve data of every type? > Teiid imported all schemas from PG > ---------------------------------- > > Key: TEIID-5963 > URL: https://issues.redhat.com/browse/TEIID-5963 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 14.0 > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > When we started teiid spring boot app, we have long start time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-204) Unable to build due to teiid wildfly connectors are not built as part of its core-release profile

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-204?focusedWorklogId=12451206&pa... ] Steven Hawkins logged work on TEIIDSB-204: ------------------------------------------ Author: Steven Hawkins Created on: 02/Jun/20 10:47 AM Start Date: 02/Jun/20 10:46 AM Worklog Time Spent: 5 hours Work Description: Time spent moving the module and updating dependencies. Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 5 hours Worklog Id: (was: 12451206) > Unable to build due to teiid wildfly connectors are not built as part of its core-release profile > ------------------------------------------------------------------------------------------------- > > Key: TEIIDSB-204 > URL: https://issues.redhat.com/browse/TEIIDSB-204 > Project: Teiid Spring Boot > Issue Type: Bug > Components: core > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > Time Spent: 5 hours > Remaining Estimate: 0 minutes > > issue on the di branch for teiid-spring-boot, https://github.com/teiid/teiid-spring-boot/blob/ca4325b98ea54266af8ee9c2a... > it references the teiid wildfly connectors > wont build because wildfly isn't built as part of teiid core-release profile -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5963) Teiid imported all schemas from PG

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5963?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5963: --------------------------------------- > And from this request (I called from db client) we got all types from all tables and schemas in DB not only from concrete schema. Yes, the driver is pulling relevant information for all types. If that is where your issue lies, then there's currently no options to disable that. We haven't come across a case before where the type information took a significant amount of time to load and the standard JDBC DatabaseMetaData interface obviously didn't anticipate any problems / need to restrict what type information is loaded either. If we offer an option to disable retrieving type info, then that would effectively disable the auto-widening of unsigned types and prevent the detection of array component types - which may not be things you care about. > Teiid imported all schemas from PG > ---------------------------------- > > Key: TEIID-5963 > URL: https://issues.redhat.com/browse/TEIID-5963 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 14.0 > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > When we started teiid spring boot app, we have long start time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5963) Teiid imported all schemas from PG

by Renat Eskenin (Jira)

[ https://issues.redhat.com/browse/TEIID-5963?page=com.atlassian.jira.plugi... ] Renat Eskenin commented on TEIID-5963: -------------------------------------- SQL executed fast, but next we have long time of messages as {code} <=BE ReadyForQuery(I) simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@8301268, maxRows=0, fetchSize=0, flags=16 FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotedocument'>,type=VARCHAR) FE=> Execute(portal=null,limit=0) FE=> Sync <=BE BindComplete [unnamed] <=BE DataRow(len=2) <=BE CommandStatus(SELECT 1) <=BE ReadyForQuery(I) simple execute, handler=org.postgresql.jdbc.PgStatement$StatementResultHandler@3bbb53f6, maxRows=0, fetchSize=0, flags=16 FE=> Bind(stmt=S_1,portal=null,$1=<'_xuotelineitem'>,type=VARCHAR) FE=> Execute(portal=null,limit=0) {code} And from this request (I called from db client) we got all types from all tables and schemas in DB not only from concrete schema. > Teiid imported all schemas from PG > ---------------------------------- > > Key: TEIID-5963 > URL: https://issues.redhat.com/browse/TEIID-5963 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 14.0 > Reporter: Renat Eskenin > Assignee: Steven Hawkins > Priority: Major > > When we started teiid spring boot app, we have long start time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 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 June 2020