[JBoss JIRA] (TEIID-2857) Build Error with Teiid POM Dependency
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2857?page=com.atlassian.jira.plugin... ]
Work on TEIID-2857 stopped by Van Halbert.
> Build Error with Teiid POM Dependency
> -------------------------------------
>
> Key: TEIID-2857
> URL: https://issues.jboss.org/browse/TEIID-2857
> Project: Teiid
> Issue Type: Bug
> Components: Embedded
> Affects Versions: 8.6
> Reporter: Ivan Chan
> Assignee: Van Halbert
> Labels: teiid
> Fix For: 8.7
>
>
> In the jboss public maven repository:
> https://repository.jboss.org/nexus/content/groups/public
> The teiid-parent-8.6.0.Final.pom file has two dependencies which look to be
> Teiid build/configuration bugs.
> These two issues are causing our source code build to fail.
> The pom file is located here:
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/teiid/...
> In this pom file there are two declared dependencies:
> <version.org.jboss.integration-platform>6.0.0-SNAPSHOT</version.org.jboss.integration-platform>
> <jbossas-version>7.2.0.Alpha1-redhat-4</jbossas-version>
> <dependency>
> <groupId>org.jboss.integration-platform</groupId>
> <artifactId>jboss-integration-platform-bom</artifactId>
> <version>${version.org.jboss.integration-platform}</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> <dependency>
> <groupId>org.jboss.as</groupId>
> <artifactId>jboss-as-parent</artifactId>
> <version>${jbossas-version}</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> Here are the issues:
> 1) Snapshot dependency existing in the 8.6.0-FINAL Release
> - jboss-integration-platform-bom/6.0.0-SNAPSHOT
> 2) Declared dependency does not exist in the repo repository.jboss.org
> - jboss-as-parent/7.2.0.Alpha1-redhat-4
> - We see dependencies only for:
> - 7.2.0.Alpha1-SNAPSHOT
> - 7.2.0.Fina
> I'm not sure why these dependencies are needed when pulling in the Teiid artifacts, but perhaps because the <scope> of
> these dependencies is set to "import" (<scope>import</scope>)
> Our usage of the repository.jboss.org is to have snapshots disabled. So that is why the 6.0.0-SNAPSHOT fails to be found.
> For the 7.2.0.Alpha1-redhat-4 dependency, it does not exist in
> repository.jboss.org so this also fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2878) Push ORDER/LIMIT for UNION query
by Tom Arnold (JIRA)
[ https://issues.jboss.org/browse/TEIID-2878?page=com.atlassian.jira.plugin... ]
Tom Arnold updated TEIID-2878:
------------------------------
Description:
Better support for queries on unions between different sources. ORDER BY is necessary on the inner queries because otherwise the result set will be truncated too early. ORDER BY can be hardcoded on the inner queries but this limits flexibility. Currently if LIMIT is not hardcoded on inner queries, ORDER BY will be stripped from query.
{code:sql}
create view v_items (...) as
select * from (
(select item_id, created_at, 'Foo' source from foo.items)
union all
(select item_id, created_at, 'Bar' source from bar.items)
) x;
-- Page 1.
select * from v_items order by created_at desc limit 0, 500;
-- Page 2.
select * from v_items order by created_at desc limit 500, 500;
{code}
was:
Better support for queries on unions between different sources. ORDER BY is necessary on the inner queries because otherwise the result set will be truncated too early. ORDER BY can be hardcoded on the inner queries but this limits flexibility.
{code:sql}
create view v_items (...) as
select * from (
(select item_id, created_at, 'Foo' source from foo.items)
union all
(select item_id, created_at, 'Bar' source from bar.items)
) x;
-- Page 1.
select * from v_items order by created_at desc limit 0, 500;
-- Page 2.
select * from v_items order by created_at desc limit 500, 500;
{code}
> Push ORDER/LIMIT for UNION query
> --------------------------------
>
> Key: TEIID-2878
> URL: https://issues.jboss.org/browse/TEIID-2878
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Priority: Minor
>
> Better support for queries on unions between different sources. ORDER BY is necessary on the inner queries because otherwise the result set will be truncated too early. ORDER BY can be hardcoded on the inner queries but this limits flexibility. Currently if LIMIT is not hardcoded on inner queries, ORDER BY will be stripped from query.
> {code:sql}
> create view v_items (...) as
> select * from (
> (select item_id, created_at, 'Foo' source from foo.items)
> union all
> (select item_id, created_at, 'Bar' source from bar.items)
> ) x;
> -- Page 1.
> select * from v_items order by created_at desc limit 0, 500;
> -- Page 2.
> select * from v_items order by created_at desc limit 500, 500;
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2878) Push ORDER/LIMIT for UNION query
by Tom Arnold (JIRA)
[ https://issues.jboss.org/browse/TEIID-2878?page=com.atlassian.jira.plugin... ]
Tom Arnold updated TEIID-2878:
------------------------------
Description:
Better support for queries on unions between different sources. ORDER BY is necessary on the inner queries because otherwise the result set will be truncated too early. ORDER BY can be hardcoded on the inner queries but this limits flexibility. Currently in 8.6 if LIMIT is not hardcoded on inner queries, ORDER BY will be stripped from query.
{code:sql}
create view v_items (...) as
select * from (
(select item_id, created_at, 'Foo' source from foo.items)
union all
(select item_id, created_at, 'Bar' source from bar.items)
) x;
-- Page 1.
select * from v_items order by created_at desc limit 0, 500;
-- Page 2.
select * from v_items order by created_at desc limit 500, 500;
{code}
was:
Better support for queries on unions between different sources. ORDER BY is necessary on the inner queries because otherwise the result set will be truncated too early. ORDER BY can be hardcoded on the inner queries but this limits flexibility. Currently if LIMIT is not hardcoded on inner queries, ORDER BY will be stripped from query.
{code:sql}
create view v_items (...) as
select * from (
(select item_id, created_at, 'Foo' source from foo.items)
union all
(select item_id, created_at, 'Bar' source from bar.items)
) x;
-- Page 1.
select * from v_items order by created_at desc limit 0, 500;
-- Page 2.
select * from v_items order by created_at desc limit 500, 500;
{code}
> Push ORDER/LIMIT for UNION query
> --------------------------------
>
> Key: TEIID-2878
> URL: https://issues.jboss.org/browse/TEIID-2878
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Priority: Minor
>
> Better support for queries on unions between different sources. ORDER BY is necessary on the inner queries because otherwise the result set will be truncated too early. ORDER BY can be hardcoded on the inner queries but this limits flexibility. Currently in 8.6 if LIMIT is not hardcoded on inner queries, ORDER BY will be stripped from query.
> {code:sql}
> create view v_items (...) as
> select * from (
> (select item_id, created_at, 'Foo' source from foo.items)
> union all
> (select item_id, created_at, 'Bar' source from bar.items)
> ) x;
> -- Page 1.
> select * from v_items order by created_at desc limit 0, 500;
> -- Page 2.
> select * from v_items order by created_at desc limit 500, 500;
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2878) Push ORDER/LIMIT for UNION query
by Tom Arnold (JIRA)
Tom Arnold created TEIID-2878:
---------------------------------
Summary: Push ORDER/LIMIT for UNION query
Key: TEIID-2878
URL: https://issues.jboss.org/browse/TEIID-2878
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 8.7
Reporter: Tom Arnold
Assignee: Steven Hawkins
Priority: Minor
Better support for queries on unions between different sources. ORDER BY is necessary on the inner queries because otherwise the result set will be truncated too early. ORDER BY can be hardcoded on the inner queries but this limits flexibility.
{code:sql}
create view v_items (...) as
select * from (
(select item_id, created_at, 'Foo' source from foo.items)
union all
(select item_id, created_at, 'Bar' source from bar.items)
) x;
-- Page 1.
select * from v_items order by created_at desc limit 0, 500;
-- Page 2.
select * from v_items order by created_at desc limit 500, 500;
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2842) Impala/ HIVE2: Unsupported compress file
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2842?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2842:
-------------------------------------
Mike, Found this page http://www.cloudera.com/content/cloudera-content/cloudera-docs/Impala/1.0...
I tried to add to my Quick Start VM but after the upgrade I am having some other issues, may be these work for you.
> Impala/ HIVE2: Unsupported compress file
> -----------------------------------------
>
> Key: TEIID-2842
> URL: https://issues.jboss.org/browse/TEIID-2842
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Impala/HIVE2 with Teiid
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: teiid
> Fix For: 8.7
>
>
> Teiid makes a query call "Describe table" in HiveMetadataProcessor.addTable(....). However, if the table contains compress file, HIVE2 driver would return the following execption:
> {code}
> java.sql.SQLException: AnalysisException: Failed to load metadata for table: default.omniturelogs
> CAUSED BY: TableLoadingException: Failed to load metadata for table:
> omniturelogs
> CAUSED BY: RuntimeException: Compressed text files are not supported: hdfs://localhost.localdomain:8020/user/cloudera/omniturelogs/Omniture.0.tsv.gz
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:161)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:149)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:182)
> at org.apache.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:246)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
> at org.teiid.translator.hive.HiveMetadataProcessor.addTable(HiveMetadataProcessor.java:112)
> at org.teiid.translator.hive.HiveMetadataProcessor.getConnectorMetadata(HiveMetadataProcessor.java:48)
>
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:311)
> ... 155 more
> {code}
> Maybe Teiid should call "DESCRIBE FORMATTED table" for table that contains compress file.
> Reference:
> http://grokbase.com/t/cloudera/impala-user/13b7c9apmx/impala-failed-to-qu...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month