[DRILL-7030] Make format plugins fully pluggable

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.15.0
• Fix Version/s: 1.17.0
• Labels: doc-impacting ready-to-commit
• Assignee: Anton Gozhiy
• Reporter: Arina Ielchiieva
• Reviewer: Arina Ielchiieva
• Created: 06/Feb/19 11:54
• Updated: 15/May/19 09:41
• Resolved: 09/May/19 03:17

Description

Discussion on the mailing list - https://lists.apache.org/thread.html/0c7de9c23ee9a8e18f8548ae0a323284cf1311b9570bd77ba544f63d@%3Cdev.drill.apache.org%3E

Before we were adding new formats / plugins into the exec module. Eventually we came up to the point that exec package size is growing and adding plugin and format contributions is better to separate out in the different module.

Now we have contrib module where we add such contributions. Plugins are pluggable, there are added automatically by means of having drill-module.conf file which points to the scanning packages.

Format plugins are using the same approach, the only problem is that they are not added into bootstrap-storage-plugins.json. So when adding new format plugin, in order for it to automatically appear in Drill Web UI, developer has to update bootstrap file which is in the exec module.

My suggestion we implement some functionality that would merge format config with the bootstrap one. For example, each plugin would have to have bootstrap-format-plugins.json file with the information to which plugin format should be added (structure the same as in bootstrap-storage-plugins.json):
Example:

{
  "storage":{
    dfs: {
      formats: {
        "psv" : {
          type: "msgpack",
          extensions: [ "mp" ]
        }
      }
    }
  }
}

Then during Drill start up such bootstrap-format-plugins.json files will be merged with bootstrap-storage-plugins.json.

Issue Links

• links to: GitHub Pull Request #1780