7 Commits

Author SHA1 Message Date
Xavier Léauté
89f821900c add imports 2013-11-13 11:51:17 -08:00
fjy
51aa7a2284 doesnt work yet 2013-11-11 14:04:03 -08:00
Gian Merlino
50a8c806c3 S3Utils: Replace S.o.println with log.warn 2013-11-02 15:24:05 -07:00
Gian Merlino
f8e564469f S3Utils: More aggressive retries, S3 can be pretty unreliable sometimes 2013-11-02 08:57:58 -07:00
fjy
1bd1bc98d1 update s3 calls to not use deprecated fns 2013-10-16 13:21:54 -07:00
fjy
9796a40b92 port docs over to 0.6 and a bunch of misc fixes 2013-10-11 18:38:53 -07:00
cheddar
c47fe202c7 Fix HadoopDruidIndexer to work with the new way of things
There are multiple and sundry changes in here.

First, "HadoopDruidIndexer" has been split into two pieces, (1) CliHadoop which pulls the hadoop version and builds up the right classpath with the proper hadoop version to run the indexer and (2) CliInternalHadoopIndexer which actually runs the indexer.

In order to work around a bunch of jets3t version conflicts with Hadoop and Druid, I needed to extract the S3 deep storage stuff into its own module.  I then also moved the HDFS stuff into its own module so that I could eliminate the dependency on Hadoop for druid-server.

In doing these changes, I wanted to make the extensions buildable with only the druid-api jar, so a few other things had to move out of Druid and into druid-api.  They are all API-level things, however, so they really belong in druid-api instead.

Lastly, I removed the druid-realtime module and put it all in druid-server.
2013-10-09 15:15:44 -05:00