Keeping in line with getting to Apache adoption, the next major refactoring stretch is to remove the old SparkJava webserver and replace it with the Jetty-based NameNodeAnalyticsHttpServer (which is just an extension / minor re-write of the Apache Hadoop NameNode webserver wrapper, NameNodeHttpServer).
This will lessen our codebase and make it even easier to manage.
Keeping in line with getting to Apache adoption, the next major refactoring stretch is to remove the old SparkJava webserver and replace it with the Jetty-based NameNodeAnalyticsHttpServer (which is just an extension / minor re-write of the Apache Hadoop NameNode webserver wrapper, NameNodeHttpServer).
This will lessen our codebase and make it even easier to manage.