Recommendations for a schema-based data language for use in Hadoop?

Hi Clojure people, I'm currently working on some problems in the big data space, and I'm more or less starting from scratch with the Hadoop ecosystem. I was looking at ways to work with data in Hadoop, and I realized that (because of how InputFormat splitting works) this is a use case where it'

RFC: Collider: Clojure's collections for Java developers

I've been developing a library that wraps Clojure's collections for use in Java 8 development: https://github.com/rschmitt/collider http://rschmitt.github.io/collider/javadoc/ Like my other major Java project, DynamicObject , the goal here is two-fold

Re: About transients no longer being safe in 1.7-alpha2

Will someone remember to update http://clojure.org/transients once 1.7.0 is released? On Monday, November 3, 2014 at 1:57:58 AM UTC-8, Daniel Marjenburgh wrote: > > Hi, > > I just want to address this issue (CLJ-1498 > ). It was accepted in > 1.7-alp

Re: Edn, Fressian, Transit: which of these formats have a future?

blicly visible. That could change in the > future. > > I am not an expert on everything you mention below but at a glance it > looks like on-point feedback and I will raise it with the appropriate > people and we can follow back here or on the relevant issues as needed. > >

Re: Edn, Fressian, Transit: which of these formats have a future?

; described. > > It has a number of other features (compression, encryption) that I may end > up using. It has given attention to backwards compatibility, and there is a > mode to turn this backwards compatibility off if it is not required. > > Lucas > > > > On 16

Edn, Fressian, Transit: which of these formats have a future?

I'm the author of dynamic-object , an open source library that makes Clojure's data modeling power available to Java programmers. This includes features like serialization and deserialization. I'll copy this small usage example from the README to give

Re: clojure.edn won't accept clojure.java.io/reader? How to work around this and why isn't this documented anywhere?

Can anyone come up with an example of a case where the call to clojure.edn/read leaves an unread character in the PushbackReader? Looking briefly at the EdnReader source, I only see cases where the pushback buffer is used internally, in order to save a character that is later consumed during th

Re: clojure.edn won't accept clojure.java.io/reader? How to work around this and why isn't this documented anywhere?

> > It turns out there are some subtle issues which can cause incorrect >> behavior were clojure.core/read to blindly wrap a PushbackReader around its >> argument: >> https://groups.google.com/d/msg/clojure/_tuypjr2M_A/W1EcEbMUg_cJ >> > > That sounds like magic. The user wrapping a PushbackReade

Re: [ANN] Initial release of dynamic-object: a library to bring Clojure data (and metadata) to Java

is would also avoid concerns about security / risk of > "eval" functionality etc. > > Also - I assume you are familiar with edn-java ( > https://github.com/bpsm/edn-java)? It would be good to make sure your > work is aligned with this > > On Thursday, 26 June 2014 07:

Re: Style-question: self-named attribute getters?

Most Clojure libraries I've seen only give you a handful of namespaces. I would expect a moderately large Clojure library to expose, say, half a dozen at most. Remember that Clojure has no concept of star imports, even for Java classes, and imports will generally be qualified somehow (e.g. cloj

[ANN] Initial release of dynamic-object: a library to bring Clojure data (and metadata) to Java

I've published the first releases of dynamic-object to Maven. dynamic-object (https://github.com/rschmitt/dynamic-object) is an effort to bring the flexibility and power of Clojure data and the Edn data language to Java developers in the most direct way possible. This library is intended to ser

Re: Style-question: self-named attribute getters?

bout "make"? Do I still implement a fruit constructor >function, or do I leave it to users to use usual hash-map constructors? > (And if I should not implement a fruit constructor, how do I indicate to >users the shape that a fruit hash-map should take? Do I just document

Re: Style-question: self-named attribute getters?

In object-oriented programming, encapsulation is always and everywhere regarded as a highly significant design virtue, but the Clojure people have a bit of a different assessment, particularly when it comes to information. In one talk, Rich Hickey pointed out that encapsulation is for hiding im

Re: Understanding when compilation occurs - for function producing functions

> Okay. Functions as values. Go look at the IFn interface, >> >> https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/IFn.java. >> >> >> > > Thanks for the link - this helps! When the clojure compiler generates a > class type that conforms to this interface, does it generate a

Re: RFC: dynamic-object, a library for working with Clojure data in Java

UTC-7, Atamert Ölçgen wrote: > > Absolutely. I don't believe consumers (of open source projects) are > entitled to anything anyway. I think it's a cool project and I hope it gets > the attention. > > > > On Tue, Jun 17, 2014 at 1:02 AM, Ryan Schmitt > wrote

Re: RFC: dynamic-object, a library for working with Clojure data in Java

se) more > people would use it and you might get more feedback then. You can always > change interfaces, conventions etc. > > > > On Mon, Jun 16, 2014 at 3:09 AM, Ryan Schmitt > wrote: > >> Set, Util, and List are actually just interfaces, and Clojure'

Re: RFC: dynamic-object, a library for working with Clojure data in Java

tion interfaces, but then I read that they're made > immutable when passed to the builder. I assume they're recursively > converted to persistent representations. > > It reminded me of Guava's immutable classes a little. (Not persistent, no > serialization) > &

RFC: dynamic-object, a library for working with Clojure data in Java

I've been developing a library to bring Clojure data to Java developers. By "Clojure data" I mean both Clojure's persistent immutable data structures *and* serialized Edn data. I wanted access to Clojure's capabilities without having to use Clojure<->Java interop directly or make use of downcas