+1
Moving forward, we'd like to evolve the format plugin API to use the new scan
framework based on the result set loader. Doing so will abstract away all the
vector-twiddling headaches that several people have had fun with over the last
couple of years. The framework will enable integration
Created Jira - https://issues.apache.org/jira/browse/DRILL-7030
Kind regards,
Arina
On Tue, Feb 5, 2019 at 4:58 PM Vitalii Diravka wrote:
> Absolutely agree with Arina.
>
> I think the core Format Plugins for Parquet, Json and CSV, TSV, PSV files
> (which are used for creating Drill tables)
Absolutely agree with Arina.
I think the core Format Plugins for Parquet, Json and CSV, TSV, PSV files
(which are used for creating Drill tables) can be left in current config
file
and the rest ones should be factored out to the separate config files along
with creating separate modules in Drill
I’d concur with Arina’s suggestion. I do think this would be useful and make
it easier to make plugins “pluggable”.
In the meantime, should we recommend that developers of format-plugins include
their plugins in the bootstrap-storage-plugins.json? I was thinking also that
we might want to
Hi all,
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