Vine v2 about carnival HOT 5 CLOSED

Not sure whether how best to go about building the new infrastructure in parallel with the old. Will start by removing extraneous references to carnival.core.vine package.

from carnival.

After doing the above, it looks like references to carnival.core.vine are now limited to the carnival.core.vine package. So, we can probably just rename current carnival.core.vine to carnival.core.vineold and start fresh with an empty carnival.core.vine package. This is a breaking change of course, but we've already introduced breaking changes. So, why not.

from carnival.

Next step is to prep the current code for the new TabularVine branch.

• rename JsonVine to Vine
• add VineMethodInterface
• JsonVineMethod implements VineMethodInterface

from carnival.

• Old vine code has been moved to carnival.core.vineold
• JsonVine has been renamed to Vine
• A initial implementation of MappedDataTableVine* is complete

There is definitely more to do. For one, there is a disparity between the cache methods of JsonVine and MappedDataTableVine. JV has a single cache file. MDTV has two. Created an object DataTableFiles to encapsulate the two files of a data table, but we should probably do something more standardized across vines. Will add an issue for this.

GenericDataTableVine* has to be added as well. Will create a separate issue. Hopefully, we can leverage inheritance and/or composition to share code between Mapped and Generic data table vines.

Also, it occurs to me that there are no facilities in the new vine classes to open/close database connections. Maybe that's ok. Will have to have a design discussion with @hjwilli. Things are probably at a good enough stopping point to merge with master.

from carnival.

Furthermore, I do think it's time to make Vine v2 a milestone. Will close this issue with next commit, create a milestone, and add finer grained tickets to it.

from carnival.