[JBoss JIRA] (TEIID-3930) Accumulo translator: select rowid returns empty resultset
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3930?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3930:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1301540
Bugzilla Update: Perform
> Accumulo translator: select rowid returns empty resultset
> ---------------------------------------------------------
>
> Key: TEIID-3930
> URL: https://issues.jboss.org/browse/TEIID-3930
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> Accumulo translator, according to its [documentation|https://docs.jboss.org/author/display/teiid812final/Apache+...], enables querying accumulo through teiid's vdb with table like:
> {code:xml}
> CREATE FOREIGN TABLE "User" (
> rowid string OPTIONS (UPDATABLE FALSE, SEARCHABLE 'All_Except_Like'),
> name_age string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'age', "teiid_accumulo:VALUE-IN" '{VALUE}'),
> name_firstname string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'firstname', "teiid_accumulo:VALUE-IN" '{VALUE}'),
> name_lastname string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'lastname', "teiid_accumulo:VALUE-IN" '{VALUE}'),
> CONSTRAINT PK0 PRIMARY KEY(rowid)
> ) OPTIONS (UPDATABLE TRUE);
> {code}
> The problem is, that querying for rowid column won't return any results:
> Query
> {code:sql}
> SELECT rowid FROM User;
> {code}
> does return empty resultset.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3930) Accumulo translator: select rowid returns empty resultset
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-3930?page=com.atlassian.jira.plugin... ]
Jan Stastny updated TEIID-3930:
-------------------------------
Description:
Accumulo translator, according to its [documentation|https://docs.jboss.org/author/display/teiid812final/Apache+...], enables querying accumulo through teiid's vdb with table like:
{code:xml}
CREATE FOREIGN TABLE "User" (
rowid string OPTIONS (UPDATABLE FALSE, SEARCHABLE 'All_Except_Like'),
name_age string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'age', "teiid_accumulo:VALUE-IN" '{VALUE}'),
name_firstname string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'firstname', "teiid_accumulo:VALUE-IN" '{VALUE}'),
name_lastname string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'lastname', "teiid_accumulo:VALUE-IN" '{VALUE}'),
CONSTRAINT PK0 PRIMARY KEY(rowid)
) OPTIONS (UPDATABLE TRUE);
{code}
The problem is, that querying for rowid column won't return any results:
Query
{code:sql}
SELECT rowid FROM User;
{code}
does return empty resultset.
was:
Accumulo translator, according to its [documentation|https://docs.jboss.org/author/display/teiid812final/Apache+...], enables querying accumulo through teiid's vdb with vdb like:
{code:xml}
CREATE FOREIGN TABLE "User" (
rowid string OPTIONS (UPDATABLE FALSE, SEARCHABLE 'All_Except_Like'),
name_age string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'age', "teiid_accumulo:VALUE-IN" '{VALUE}'),
name_firstname string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'firstname', "teiid_accumulo:VALUE-IN" '{VALUE}'),
name_lastname string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'lastname', "teiid_accumulo:VALUE-IN" '{VALUE}'),
CONSTRAINT PK0 PRIMARY KEY(rowid)
) OPTIONS (UPDATABLE TRUE);
{code}
The problem is, that querying for rowid column won't return any results:
Query
{code:sql}
SELECT rowid FROM User;
{code}
does return empty resultset.
> Accumulo translator: select rowid returns empty resultset
> ---------------------------------------------------------
>
> Key: TEIID-3930
> URL: https://issues.jboss.org/browse/TEIID-3930
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> Accumulo translator, according to its [documentation|https://docs.jboss.org/author/display/teiid812final/Apache+...], enables querying accumulo through teiid's vdb with table like:
> {code:xml}
> CREATE FOREIGN TABLE "User" (
> rowid string OPTIONS (UPDATABLE FALSE, SEARCHABLE 'All_Except_Like'),
> name_age string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'age', "teiid_accumulo:VALUE-IN" '{VALUE}'),
> name_firstname string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'firstname', "teiid_accumulo:VALUE-IN" '{VALUE}'),
> name_lastname string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'lastname', "teiid_accumulo:VALUE-IN" '{VALUE}'),
> CONSTRAINT PK0 PRIMARY KEY(rowid)
> ) OPTIONS (UPDATABLE TRUE);
> {code}
> The problem is, that querying for rowid column won't return any results:
> Query
> {code:sql}
> SELECT rowid FROM User;
> {code}
> does return empty resultset.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3930) Accumulo translator: select rowid returns empty resultset
by Jan Stastny (JIRA)
Jan Stastny created TEIID-3930:
----------------------------------
Summary: Accumulo translator: select rowid returns empty resultset
Key: TEIID-3930
URL: https://issues.jboss.org/browse/TEIID-3930
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.3
Reporter: Jan Stastny
Assignee: Steven Hawkins
Accumulo translator, according to its [documentation|https://docs.jboss.org/author/display/teiid812final/Apache+...], enables querying accumulo through teiid's vdb with vdb like:
{code:xml}
CREATE FOREIGN TABLE "User" (
rowid string OPTIONS (UPDATABLE FALSE, SEARCHABLE 'All_Except_Like'),
name_age string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'age', "teiid_accumulo:VALUE-IN" '{VALUE}'),
name_firstname string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'firstname', "teiid_accumulo:VALUE-IN" '{VALUE}'),
name_lastname string OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_accumulo:CF" 'name', "teiid_accumulo:CQ" 'lastname', "teiid_accumulo:VALUE-IN" '{VALUE}'),
CONSTRAINT PK0 PRIMARY KEY(rowid)
) OPTIONS (UPDATABLE TRUE);
{code}
The problem is, that querying for rowid column won't return any results:
Query
{code:sql}
SELECT rowid FROM User;
{code}
does return empty resultset.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3929) Accumulo does not return null values
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3929:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1301527
Bugzilla Update: Perform
> Accumulo does not return null values
> ------------------------------------
>
> Key: TEIID-3929
> URL: https://issues.jboss.org/browse/TEIID-3929
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> Accumulo doesn't return null values when a whole 'column' is being selected.
> For a command in accumulo shell like:
> {code:plain}
> scan -c name:BYTENUM
> {code}
> Accumulo returns only non-empty values, this is expected behaviour.
> Equivalent query in Teiid would be:
> {code:sql}
> SELECT ByteNum FROM SmallA
> {code}
> Which returns the same results as Accumulo does. That means, no NULL values, if there are rowids without specified column families/qualifiers missing. But when a user has his schema defined in a vdb, he probably expects, that he will get as many rows as there are in the table.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3929) Accumulo does not return null values
by Jan Stastny (JIRA)
Jan Stastny created TEIID-3929:
----------------------------------
Summary: Accumulo does not return null values
Key: TEIID-3929
URL: https://issues.jboss.org/browse/TEIID-3929
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.3
Reporter: Jan Stastny
Assignee: Steven Hawkins
Accumulo doesn't return null values when a whole 'column' is being selected.
For a command in accumulo shell like:
{code:plain}
scan -c name:BYTENUM
{code}
Accumulo returns only non-empty values, this is expected behaviour.
Equivalent query in Teiid would be:
{code:sql}
SELECT ByteNum FROM SmallA
{code}
Which returns the same results as Accumulo does. That means, no NULL values, if there are rowids without specified column families/qualifiers missing. But when a user has his schema defined in a vdb, he probably expects, that he will get as many rows as there are in the table.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3927) Teiid Analytical Capabilities
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3927?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-3927:
-------------------------------
Description:
>From DV 7(teiid 9.x) F2F notes, Analytical Capabilities be referred in 2 approach:
h2. Do our own
* Support for row counts beyond 2 billion (done)
* Increased parallism within the plan, which includes parallelization of source queries via partitioning beyond multi-source
* Increased windowing function support
h2. Alignment with a larger platform
TEIID-3928
was:
>From DV 7(teiid 9.x) F2F notes, Analytical Capabilities be referred in 2 approach:
h2. Do our own
* Support for row counts beyond 2 billion (done)
* Increased parallism within the plan, which includes parallelization of source queries via partitioning beyond multi-source
* Increased windowing function support
h2. Alignment with a larger platform
Sub-Task
> Teiid Analytical Capabilities
> -----------------------------
>
> Key: TEIID-3927
> URL: https://issues.jboss.org/browse/TEIID-3927
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.x
>
>
> From DV 7(teiid 9.x) F2F notes, Analytical Capabilities be referred in 2 approach:
> h2. Do our own
> * Support for row counts beyond 2 billion (done)
> * Increased parallism within the plan, which includes parallelization of source queries via partitioning beyond multi-source
> * Increased windowing function support
> h2. Alignment with a larger platform
> TEIID-3928
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3928) Alignment with a larger platform
by Kylin Soong (JIRA)
Kylin Soong created TEIID-3928:
----------------------------------
Summary: Alignment with a larger platform
Key: TEIID-3928
URL: https://issues.jboss.org/browse/TEIID-3928
Project: Teiid
Issue Type: Sub-task
Affects Versions: 9.x
Reporter: Kylin Soong
Assignee: Kylin Soong
Fix For: 9.x
Copy from Teiid 9.x DV7 F2F Notes
{note}
We should promote with analytical platforms, such as Spark/Hive/PrestoDB, are usages of Teiid/DV as a data loader (we support a wider variety of sources can have views that perform incoming transformation/filtering logic) and for top level integration (since we provide more robust client support, transaction support, and broader federation). Those usages present a cooperative pairing with an analytical platform - however we know that over time these projects will continue to creep into the virtualization space as users need more robust odbc/jdbc, write/oltp workload support, etc.
As an organization we may align with the Spark platform / ecosystem. If that is the case, then we will give heavy preference to Spark integration.
{note}
h2. Task we need do
Spend time on Spark integration, Write document, Add integration code, sample code.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3927) Teiid Analytical Capabilities
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3927?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-3927:
-------------------------------
Description:
>From DV 7(teiid 9.x) F2F notes, Analytical Capabilities be referred in 2 approach:
h2. Do our own
* Support for row counts beyond 2 billion (done)
* Increased parallism within the plan, which includes parallelization of source queries via partitioning beyond multi-source
* Increased windowing function support
h2. Alignment with a larger platform
Sub-Task
was:
>From DV 7 F2F notes, Analytical Capabilities be referred in 2 approach:
h2. Do our own
* Support for row counts beyond 2 billion (done)
* Increased parallism within the plan, which includes parallelization of source queries via partitioning beyond multi-source
* Increased windowing function support
h2. Alignment with a larger platform
Sub-Task
> Teiid Analytical Capabilities
> -----------------------------
>
> Key: TEIID-3927
> URL: https://issues.jboss.org/browse/TEIID-3927
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.x
>
>
> From DV 7(teiid 9.x) F2F notes, Analytical Capabilities be referred in 2 approach:
> h2. Do our own
> * Support for row counts beyond 2 billion (done)
> * Increased parallism within the plan, which includes parallelization of source queries via partitioning beyond multi-source
> * Increased windowing function support
> h2. Alignment with a larger platform
> Sub-Task
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3927) Teiid Analytical Capabilities enhancement
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3927?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-3927:
-------------------------------
Description:
>From DV 7 F2F notes, Analytical Capabilities be referred in 2 approach:
h2. Do our own
* Support for row counts beyond 2 billion (done)
* Increased parallism within the plan, which includes parallelization of source queries via partitioning beyond multi-source
* Increased windowing function support
h2. Alignment with a larger platform
Sub-Task
was:
>From DV 7 F2F notes, Analytical Capabilities be referred in 2 approach:
h3. Do our own
* Support for row counts beyond 2 billion (done)
* Increased parallism within the plan, which includes parallelization of source queries via partitioning beyond multi-source
* Increased windowing function support
h3. Alignment with a larger platform
Sub-Task
> Teiid Analytical Capabilities enhancement
> -----------------------------------------
>
> Key: TEIID-3927
> URL: https://issues.jboss.org/browse/TEIID-3927
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.x
>
>
> From DV 7 F2F notes, Analytical Capabilities be referred in 2 approach:
> h2. Do our own
> * Support for row counts beyond 2 billion (done)
> * Increased parallism within the plan, which includes parallelization of source queries via partitioning beyond multi-source
> * Increased windowing function support
> h2. Alignment with a larger platform
> Sub-Task
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3927) Teiid Analytical Capabilities
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3927?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-3927:
-------------------------------
Summary: Teiid Analytical Capabilities (was: Teiid Analytical Capabilities enhancement)
> Teiid Analytical Capabilities
> -----------------------------
>
> Key: TEIID-3927
> URL: https://issues.jboss.org/browse/TEIID-3927
> Project: Teiid
> Issue Type: Feature Request
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.x
>
>
> From DV 7 F2F notes, Analytical Capabilities be referred in 2 approach:
> h2. Do our own
> * Support for row counts beyond 2 billion (done)
> * Increased parallism within the plan, which includes parallelization of source queries via partitioning beyond multi-source
> * Increased windowing function support
> h2. Alignment with a larger platform
> Sub-Task
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months