[JBoss JIRA] (TEIID-5965) Allow variables to be used as TextTable delimeters, row delimeters, quote, header, skip rows, and escape characters
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5965?page=com.atlassian.jira.plugi... ]
Work on TEIID-5965 started by Steven Hawkins.
---------------------------------------------
> Allow variables to be used as TextTable delimeters, row delimeters, quote, header, skip rows, and escape characters
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-5965
> URL: https://issues.redhat.com/browse/TEIID-5965
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 13.1
> Reporter: Dmitrii Pogorelov
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0
>
> Original Estimate: 5 hours
> Remaining Estimate: 5 hours
>
> In the specified example, the delimiter is TAB. Many web APIs allow customization of the delimiter character, and in order to provide a generic parser, sometimes it is way easier to define a delimiter as a variable, and not need to create a long nested structure with IF-THEN-ELSE-IF-ELSE constructs:
> {code:sql}
> Select * From TextTable (
> 'c1 c2
> 1 2'
> Columns
> c1 integer,
> c2 integer
> Delimiter E'\t'
> Header 1
> )x;
> {code}
> Imagine that based on setup on API side (out of our control) the content can be delivered via tab or semicolon, e.g.
> {code}
> c1;c2
> 1;2
> {code}
> or
> {code}
> c1 c2
> 1 2
> {code}
> Let's save this response into a variable and see the code, which we will need to write depending on the setup:
> {code:sql}
> Begin
> ...
> If (delimiter = 'tab')
> Begin
> Select * From TextTable (
> apiResponse
> Columns
> c1 integer,
> c2 integer
> Delimiter E'\t'
> Header 1
> )x;
> End
> Else If (delimiter = 'tab')
> Begin
> Select * From TextTable (
> apiResponse
> Columns
> c1 integer,
> c2 integer
> Delimiter ';'
> Header 1
> )x;
> End
> End
> {code}
> The if-else block is constantly growing, especially if we want to customize quote, escape, delimiter, and row delimiter.
> Thus it would be great if we could make these values configurable. In this case, we could end up with this expected code, which is more readable and more easily customizable:
> {code:sql}
> Begin
> ...
> Declare string delimiter = E'\t';
> Select * From TextTable (
> apiResponse
> Columns
> c1 integer,
> c2 integer
> Delimiter delimiter
> Header 1
> )x;
> End
> {code}
> With a bit of tweaking and certain assumptions, leading in the trust level, we can even read the first line and try to auto-detect the delimiter automatically (e.g. by counting tabs, commas, and semicolons in the first line).
> Please, could you be so kind as to make HEADER and SKIP values customizable (rather than hardcoded numbers)?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (TEIID-5928) Allow External and Internal materialization of multi-source to fail/update individually
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5928?page=com.atlassian.jira.plugi... ]
Work on TEIID-5928 started by Steven Hawkins.
---------------------------------------------
> Allow External and Internal materialization of multi-source to fail/update individually
> ---------------------------------------------------------------------------------------
>
> Key: TEIID-5928
> URL: https://issues.redhat.com/browse/TEIID-5928
> Project: Teiid
> Issue Type: Enhancement
> Components: Common
> Affects Versions: 12.2.2
> Reporter: Rafael Sampaio
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 15.0
>
> Original Estimate: 0 minutes
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> Hi, all.
> First of all thanks in advance for your attention, and efforts on such a great product.
> Since I haven't found any docs or examples regarding my current usage (please if this already exists or there's a better way of doing this, disregard this request and advice) here goes my suggestion:
> It would be nice to have a way to gracefully update/fail per source, if a view that has Materialization enabled and target a multi-source source model, because things can get, messy if I have to create a view per source and Materialize each one and only then create a unified (UNION) view.
> Using this approach also obligates me to implement custom insert/update/delete/based on the discriminator column.
> Thanks again.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[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?focusedWorklogId=12451577&pa... ]
Steven Hawkins logged work on TEIIDSB-206:
------------------------------------------
Author: Steven Hawkins
Created on: 24/Jun/20 11:52 AM
Start Date: 24/Jun/20 11:52 AM
Worklog Time Spent: 1 hour, 30 minutes
Work Description: Brought the teiid changes over and logged additional issues.
Issue Time Tracking
-------------------
Remaining Estimate: 1 day, 7 hours (was: 2 days, 30 minutes)
Time Spent: 5 hours (was: 3 hours, 30 minutes)
Worklog Id: (was: 12451577)
> 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
>
> Original Estimate: 2 days, 4 hours
> Time Spent: 5 hours
> Remaining Estimate: 1 day, 7 hours
>
> 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)
5 years, 5 months
[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 commented on TEIIDSB-206:
----------------------------------------
The remaining tasks here are to add the hdfs mustache file, an hdfs sample, and a crd. [~adityamanglam] will handle the first two.
> 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
>
> Original Estimate: 2 days, 4 hours
> Time Spent: 3 hours, 30 minutes
> Remaining Estimate: 2 days, 30 minutes
>
> 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)
5 years, 5 months
[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 commented on TEIIDSB-206:
----------------------------------------
> This can be well covered in the Operator as in Operator we have
Since this problem really only affects the operator path, it should be fine to resolve it using datasources rather than requiring a ddl change. We can of course ensure that create server type matches with what is specified in datasources, or just reserve it for future use like we did for fdw handler.
I'll put in an issue for that and one to correct the existing ftp and hdfs translator names.
> 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
>
> Original Estimate: 2 days, 4 hours
> Time Spent: 3 hours, 30 minutes
> Remaining Estimate: 2 days, 30 minutes
>
> 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)
5 years, 5 months
[JBoss JIRA] (TEIIDSB-209) NPE using salesforce connection
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-209?page=com.atlassian.jira.plug... ]
Steven Hawkins resolved TEIIDSB-209.
------------------------------------
Resolution: Done
Properly fixed this upstream with additional changes to better encapsulate the state creation. For the product branch the one line fix was added.
> NPE using salesforce connection
> -------------------------------
>
> Key: TEIIDSB-209
> URL: https://issues.redhat.com/browse/TEIIDSB-209
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.6.0
>
> Original Estimate: 30 minutes
> Time Spent: 30 minutes
> Remaining Estimate: 0 minutes
>
> The config is not being set appropriately and results in an npe. This is due to TEIIDSB-184
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (TEIIDSB-209) NPE using salesforce connection
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-209?focusedWorklogId=12451570&pa... ]
Steven Hawkins logged work on TEIIDSB-209:
------------------------------------------
Author: Steven Hawkins
Created on: 23/Jun/20 1:49 PM
Start Date: 23/Jun/20 1:49 PM
Worklog Time Spent: 1 hour
Issue Time Tracking
-------------------
Time Spent: 1 hour, 30 minutes (was: 30 minutes)
Worklog Id: (was: 12451570)
> NPE using salesforce connection
> -------------------------------
>
> Key: TEIIDSB-209
> URL: https://issues.redhat.com/browse/TEIIDSB-209
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: datasource
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.6.0
>
> Original Estimate: 30 minutes
> Time Spent: 1 hour, 30 minutes
> Remaining Estimate: 0 minutes
>
> The config is not being set appropriately and results in an npe. This is due to TEIIDSB-184
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months