Bud v0.0.6 released

8 views
Skip to first unread message

Neil Conway

unread,
Oct 10, 2011, 1:17:38 AM10/10/11
to bloom...@googlegroups.com
Bud 0.0.6 has been released, and is available for download via RubyGems.

This release includes two primary fixes:

(1) Correctness fixes for the newly-introduced anti-join (negation)
syntax. Anyone using the `notin` syntax is strongly encouraged to
upgrade.

(2) Compatibility fixes for ruby2ruby 1.3.1. Specifically, ruby2ruby
1.3.1 has a bug which impacts Bud, so the 0.0.6 release depends on
ruby2ruby < 1.3.1.

The release also includes a bunch of other fixes, including:

* Change the behavior of BudCollection#schema. This previously
returned the column names of the collection as a list. Instead,
#schema will now return a hash: { key_col_names => non_key_col_names
}. The previous #schema behavior is available via BudCollection#cols.

* Reject import of modules that have already included the Bud module

* Disallow schemas containing "@" for non-channel collections

* Various budplot and visualization improvements

* Minor performance improvements

On behalf of the Bloom folks:

Peter Alvaro
Peter Bailis
Neil Conway
Joe Hellerstein
Bill Marczak

Neil

qihui sun

unread,
Oct 10, 2011, 10:29:56 AM10/10/11
to bloom...@googlegroups.com
Good news,to expect the 1.0 version!
And have any plan to migrate to Scala@JVM as a DSL? For example ,like Orc language project(http://orc.csres.utexas.edu/).
Thanks.

2011/10/10 Neil Conway <n...@eecs.berkeley.edu>



--
QQ:103561996

Joe Hellerstein

unread,
Oct 10, 2011, 10:52:14 AM10/10/11
to bloom...@googlegroups.com
We are actively discussing other language targets in our group, and are looking seriously at Scala and other JVM languages.

Roadmap for 1.0 is still wide open, but I expect it will include JRuby as well as language targets outside of Ruby. This will become more clear in coming months.

Thanks for your interest!
J

Neil Conway

unread,
Oct 10, 2011, 7:26:48 PM10/10/11
to bloom...@googlegroups.com
We recently discovered another bug in the anti-join code. That bug has
been fixed, and a new gem (v0.0.7) has been pushed to RubyGems with
the fix.

Neil

Reply all
Reply to author
Forward
0 new messages