There have been multiple discussions about Druid source having too many sub-projects which really doesn't provide much value and often leads to complications e.g. server/src/main/java/io/druid/client/indexing/ClientXXXQuery.java classes are equivalent to XXXTask.java classes in indexing-service/ and needs to stay in sync .. more such classes are created in #5102 .
similar desire has been mentioned in metamx/java-util#74 (comment) and #5102 (comment) .
So, here is my initial idea....
- merge
druid-api, druid-commons, java-utils, druid-processing into druid-core
- merge
druid-server, druid-indexing-service into druid-server
we can merge things further if necessary.
There have been multiple discussions about Druid source having too many sub-projects which really doesn't provide much value and often leads to complications e.g.
server/src/main/java/io/druid/client/indexing/ClientXXXQuery.javaclasses are equivalent toXXXTask.javaclasses inindexing-service/and needs to stay in sync .. more such classes are created in #5102 .similar desire has been mentioned in metamx/java-util#74 (comment) and #5102 (comment) .
So, here is my initial idea....
druid-api, druid-commons, java-utils, druid-processingintodruid-coredruid-server, druid-indexing-serviceintodruid-serverwe can merge things further if necessary.