September 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4525) postgresql translator - remove all nulls & non printable characters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4525?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4525: ---------------------------------- Fix Version/s: 10.x (was: Open To Community) (was: 10.0) > postgresql translator - remove all nulls & non printable characters > ------------------------------------------------------------------- > > Key: TEIID-4525 > URL: https://issues.jboss.org/browse/TEIID-4525 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Omar Khan > Priority: Minor > Fix For: 10.x > > > Would like to see the postgresql translator enhanced to add a feature to minimum remove nulls from text strings as some other databases i.e. Teradata allow for them where Postgres does not. This feature would behave in a similar manner as TrimSpaces, but simply remove all \u0000 characters. > Furthermore, if possible, would like the ability to remove non printable characters to as another option provide another additional stripping mechanism, allowing the postgresql database to serve as a data cleaner if need be. > Please refer to https://developer.jboss.org/thread/272644 for details -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3738) Add multi-tenant functionality

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3738?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3738: ---------------------------------- Fix Version/s: 10.x (was: 10.0) > Add multi-tenant functionality > ------------------------------ > > Key: TEIID-3738 > URL: https://issues.jboss.org/browse/TEIID-3738 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors, Query Engine > Reporter: Steven Hawkins > Fix For: 10.x > > > To supplement multi-source functionality, we should add explicit multi-tenant functionality similar to hibernate - http://docs.jboss.org/hibernate/orm/4.2/devguide/en-US/html/ch16.html > This would mostly be carried out at the datasource level, but would also make us cache aware. Otherwise our current story is to implement multi-source and add row level filters to all multi-source tables to prune based upon the user - which we could choose to expand on in Designer or the server such that the necessary roles are created automatically. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3868) Add a json type with search support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3868?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3868: ---------------------------------- Fix Version/s: 10.x (was: 10.0) > Add a json type with search support > ----------------------------------- > > Key: TEIID-3868 > URL: https://issues.jboss.org/browse/TEIID-3868 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 9.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.x > > > We should add a json type similar to the json/jsonb types from postgresql. Additional construction and especially search support should added so that most common scenarios will not need intermediate xml processing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3280) Embedded Teiid | VDB scoped translators

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3280?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3280: ---------------------------------- Fix Version/s: 10.x (was: 10.0) > Embedded Teiid | VDB scoped translators > ----------------------------------------- > > Key: TEIID-3280 > URL: https://issues.jboss.org/browse/TEIID-3280 > Project: Teiid > Issue Type: Enhancement > Components: Embedded > Reporter: Shiveeta Mattoo > Assignee: Steven Hawkins > Priority: Minor > Fix For: 10.x > > > - Translator instances, once created are applicable for all VDB deployment invocations. > - Seeking support for VDB scoped translators which could enable configuring properties for translators specific to VDB instances. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2703) Refactor value retrieval to class based

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2703?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2703: ---------------------------------- Fix Version/s: 10.x (was: 10.0) > Refactor value retrieval to class based > --------------------------------------- > > Key: TEIID-2703 > URL: https://issues.jboss.org/browse/TEIID-2703 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.x > > > Similar to Hibernate, we need to introduce encapsulated value retrieval methods. The current approach (which is legacy back to the mmx days) typically uses a switch block with other checks, which can largely be avoided and should improve performance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4438) Crate ability to filter include/exclude tables during the import across all translators

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4438?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4438: ---------------------------------- Fix Version/s: 10.x (was: 10.0) > Crate ability to filter include/exclude tables during the import across all translators > --------------------------------------------------------------------------------------- > > Key: TEIID-4438 > URL: https://issues.jboss.org/browse/TEIID-4438 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Ramesh Reddy > Fix For: 10.x > > > Currently only JDBC translator allows exclude tables, inclusion and exclusion of tables to import during the metadata import needs to be added as generic feature across all translators to support TEIID-2578's DDL import command > IMPORT FOREIGN SCHEMA .. INCLUDE .. EXCLUDE .. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3537) Use array binding for postgresql dependent join

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3537?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3537: ---------------------------------- Fix Version/s: 10.x (was: 10.0) > Use array binding for postgresql dependent join > ----------------------------------------------- > > Key: TEIID-3537 > URL: https://issues.jboss.org/browse/TEIID-3537 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.x > > > Rather than creating a large sql statement or rely upon a small fixed limit to the number of binding, we can bind array values to perform dependent query comparisons - where id = ANY ? > This however only seems to work for single values or composites of the same type. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4500) Make documents to capable of building outside the GitBooks

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4500?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4500: ------------------------------------- Assignee: Ramesh Reddy > Make documents to capable of building outside the GitBooks > ---------------------------------------------------------- > > Key: TEIID-4500 > URL: https://issues.jboss.org/browse/TEIID-4500 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 10.0 > > > Currently Teiid documentation is only built by automated process by GitBooks. However, this causes couple issues > * There is no way to check the documentation formatting external to the GitBook. > * Documents need to be always hosted by the Gitbook. I am sure there is way to export, but that may need human to do that? Going forward we would need a automated way if one wants to bundle the documents. > * Gitbook only allows two books for free, we already against this limit with no resolution with the paid route. > Thus it may be better we also have alternative ways to generate final documents, and be able to host on teiid.org. I find an example with Infinispan documents, we just need to mimic what they are doing > >> We have also implemented generation of PDFs via the > > > asciidoctor-maven-plugin with optimized post-processing via GhostScript > > > (which shrinks the size of the PDFs to a 1/4 of the size). > > > Look at [2] and [3] to see how that is done. > > > > > > Tristan > > > > > > [1] http://infinispan.org/docs/dev/user_guide/user_guide.html > > > [2] > > > https://github.com/infinispan/infinispan/blob/master/documentation/pom.xml > > > [3] > > > https://github.com/infinispan/infinispan/blob/master/documentation/optimi... > also look at their google-analytics stuff, that is very useful to have. I do also like Infinispans style sheets better than the current default GitBook's, we should adapt them too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5012) Add the VDB description and creation timestamp information to the Sys.Virtualdatabases table as new columns (Database Description, Database Creation timestamp)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5012?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5012: --------------------------------------- > that could instead be looked up in the properties Actually it cannot. We don't add the properties to that table, nor is there a uid assigned to a vdb. I'll have to see if something else makes sense. > Add the VDB description and creation timestamp information to the Sys.Virtualdatabases table as new columns (Database Description, Database Creation timestamp) > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-5012 > URL: https://issues.jboss.org/browse/TEIID-5012 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Tom Johnston > Assignee: Steven Hawkins > Priority: Minor > Fix For: 10.0 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1131) Document/expand sequence support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1131?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1131: --------------------------------------- > Does DatabaseMetadata give import facilities for the sequences? Only pg, and even that is an undocumented feature. > Document/expand sequence support > -------------------------------- > > Key: TEIID-1131 > URL: https://issues.jboss.org/browse/TEIID-1131 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector, Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > Currently sequence workaround logic only exists for oracle and is undocumented. We should look at expanding sequence support - even for dynamic vdbs, see SQuriel's handling of system queries for retrieving sequence metadata. > At least allowing the workaround logic to work for all sources that support sequences (Postgres, DB2, etc.) would be good. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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