7 Commits

Author	SHA1	Message	Date
fjy	713015199a	[maven-release-plugin] prepare release druid-0.6.1	2013-11-05 15:42:33 -08:00
fjy	a684885839	[maven-release-plugin] prepare for next development iteration	2013-10-18 15:48:16 -07:00
fjy	88dcfe9a94	[maven-release-plugin] prepare release druid-0.6.0	2013-10-18 15:48:12 -07:00
fjy	2dc716bf7e	fix bug and make it actually possible to load extensions	2013-10-16 11:59:01 -07:00
fjy	9796a40b92	port docs over to 0.6 and a bunch of misc fixes	2013-10-11 18:38:53 -07:00
fjy	a9a723bd11	clean up poms, add a new loading your own data tutorial, add new validation, clean up logs	2013-10-09 15:42:39 -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