Getting the Error: All inputs to rbind.fill must be data.frames after upgrade to rmr 3.2

1,283 views
Skip to first unread message

sravan kumar

unread,
Oct 9, 2014, 10:18:00 AM10/9/14
to rha...@googlegroups.com
Hi,

I have recently upgraded my RMR version from 3.1 to 3.2 and the leftouterjoin fails with the error Error: All inputs to rbind.fill must be data.frames
It was running fine with RMR version 3.1

My R version is 3.1. It is failing in R 3.0.2 too.

Code snippet for which it is giving me the error.

library(rmr2)
library(rhdfs)
rmr.options(backend = "local")

df1<-data.frame(a=c(1:4),b=c(6:9))
df2<-data.frame(d=c(6:9),e=c(6:9))
input1 <- to.dfs(list(key=df1,val=df2))

df3<-data.frame(a=c(1:3),b=c(6:8))
df4<-data.frame(d=c(1:3),e=c(1:3))
input2 <- to.dfs(list(key=df3,val=df4))

reducer = function(key, left, right) {
    if(!class(right)=="data.frame")
        output.val=left
    else
        output.val=right
    keyval(key,left)
}

output<-equijoin(
    left.input = input1, 
    right.input = input2, 
    outer = c("left"),    
    reduce  = reducer)


Antonio Piccolboni

unread,
Oct 9, 2014, 11:28:59 AM10/9/14
to RHadoop Google Group
Thanks for this report and the self contained test case, that's a model of how to report a problem. This is now bug 144. Please follow any progress there.

--
post: rha...@googlegroups.com ||
unsubscribe: rhadoop+u...@googlegroups.com ||
web: https://groups.google.com/d/forum/rhadoop?hl=en-US
---
You received this message because you are subscribed to the Google Groups "RHadoop" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rhadoop+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

sravan kumar

unread,
Oct 9, 2014, 12:56:22 PM10/9/14
to rha...@googlegroups.com, ant...@piccolboni.info
Thanks Antonio, for the quick reply and for raising the bug. Is there any work around for the these outerjoins in the latest version?

Antonio Piccolboni

unread,
Oct 9, 2014, 1:05:03 PM10/9/14
to RHadoop Google Group
This was actually reported and fixed. Not sure what's going on. Please let's not have two threads on this, this is now on the issue tracker.
Reply all
Reply to author
Forward
0 new messages