Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Sprint:DB_S17_5
-
Team:Data Access and Database
Description
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the ForcedSource table of WISE catalog (database wise_00) which correspond to the rejected objects of the catalog (those objects live in a separate database wise_ext_00):
SELECT COUNT(ForcedSource.source_id_mf) |
FROM |
wise_ext_00.Reject Reject,
|
wise_00.ForcedSource ForcedSource
|
WHERE |
Reject.source_id LIKE '0000m016_ac51-000002' |
AND ForcedSource.source_id_mf = Reject.source_id; |
ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves |
partitioned table joins that Qserv does not know how to evaluate using only partition-local data |
The only relevant line in the CZAR's log file is:
[2017-04-21T16:01:43.412-0500] [LWP:346] ERROR ccontrol.UserQueryFactory (core/modules/ccontrol/UserQueryFactory.cc:114)
|
- Invalid query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate
|
using only partition-local data
|
Attachments
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Rank | Ranked higher |
Priority | Undefined [ 10000 ] | Major [ 3 ] |
Status | To Do [ 10001 ] | In Progress [ 3 ] |
Description | Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time. |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {sql} |
Description |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {sql} |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} |
Description |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} |
Description |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} |
Description |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} The only relevant line in the *CZAR*'s log file is: {code} [2017-04-21T16:01:43.412-0500] [LWP:346] ERROR ccontrol.UserQueryFactory (core/modules/ccontrol/UserQueryFactory.cc:114) - Invalid query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} |
Description |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} The only relevant line in the *CZAR*'s log file is: {code} [2017-04-21T16:01:43.412-0500] [LWP:346] ERROR ccontrol.UserQueryFactory (core/modules/ccontrol/UserQueryFactory.cc:114) - Invalid query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} The only relevant line in the *CZAR*'s log file is: {code} [2017-04-21T16:01:43.412-0500] [LWP:346] ERROR ccontrol.UserQueryFactory (core/modules/ccontrol/UserQueryFactory.cc:114) - Invalid query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} |
Description |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} The only relevant line in the *CZAR*'s log file is: {code} [2017-04-21T16:01:43.412-0500] [LWP:346] ERROR ccontrol.UserQueryFactory (core/modules/ccontrol/UserQueryFactory.cc:114) - Invalid query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} |
Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.
An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*): {code:sql} SELECT COUNT(ForcedSource.source_id_mf) FROM wise_ext_00.Reject Reject, wise_00.ForcedSource ForcedSource WHERE Reject.source_id LIKE '0000m016_ac51-000002' AND ForcedSource.source_id_mf = Reject.source_id; ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} The only relevant line in the *CZAR*'s log file is: {code} [2017-04-21T16:01:43.412-0500] [LWP:346] ERROR ccontrol.UserQueryFactory (core/modules/ccontrol/UserQueryFactory.cc:114) - Invalid query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate using only partition-local data {code} |
Sprint | DB_S17_5 [ 615 ] |
Reviewers | Andy Salnikov, Igor Gaponenko [ salnikov, gapon ] | |
Status | In Progress [ 3 ] | In Review [ 10004 ] |
Resolution | Done [ 10000 ] | |
Status | In Review [ 10004 ] | Done [ 10002 ] |