[ 
https://issues.apache.org/jira/browse/MRQL-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137594#comment-15137594
 ] 

Hudson commented on MRQL-81:
----------------------------

SUCCESS: Integrated in mrql-master-snapshot #24 (See 
[https://builds.apache.org/job/mrql-master-snapshot/24/])
[MRQL-81] Fix the coercion of persistent collections to in-memory bags 
(fegaras: 
[https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git&a=commit&h=aceab31597bd33d7d22c457a053084976b39ac91])
* core/src/main/java/org/apache/mrql/Printer.gen
* flink/src/main/java/org/apache/mrql/FlinkEvaluator.gen
* mapreduce/src/main/java/org/apache/mrql/MapReduceEvaluator.gen
* core/src/main/java/org/apache/mrql/QueryPlan.gen
* queries/factorization.mrql
* queries/factorization3.mrql
* bsp/src/main/java/org/apache/mrql/BSPEvaluator.gen
* core/src/main/java/org/apache/mrql/Evaluator.java
* spark/src/main/java/org/apache/mrql/SparkEvaluator.gen


> Fix the coercion of persistent collections to in-memory bags 
> -------------------------------------------------------------
>
>                 Key: MRQL-81
>                 URL: https://issues.apache.org/jira/browse/MRQL-81
>             Project: MRQL
>          Issue Type: Bug
>          Components: Run-Time/Flink, Run-Time/MapReduce, Run-Time/Spark
>    Affects Versions: 0.9.6
>            Reporter: Leonidas Fegaras
>            Assignee: Leonidas Fegaras
>            Priority: Critical
>
> Currently, query results that are persistent bags (such as Spark RDDs or 
> Flink DataSets) are coerced to in-memory bags before they are printed. This 
> needs to be done at any place in the query result. This came out when we used 
> matrix factorization (query/factorization.mrql) because its output are the 
> two matrix factors (datasets) in a tuple. It was reported by Ahmed Ulde. It 
> will be fixed by adding a new case for tuple projection in the query 
> evaluator that coerces persistent datasets to bags when they appear in the 
> query output.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to