Josh Elser

> there are some limitations in MonitoredTask which doesn't allow me to track start time and end time for each state. Also it doesn't show the states that are completed....

> It's tricky to find out which StatusJournalEntry are the same. How about we keep the last 500 status in memory and evict the older ones ? That's acceptable to...

Oh bother, now I see #3936 has the same changes.

A "dumb" solution would be to encourage a shaded jar with relocated classes. Very inelegant when compared to a solution like OSGI or felix and requires more work to build...

> Thanks for pointing that out, that may be a good way to go. If nothing else, it's not bad to isolate the Fluo dependencies that way. Forcing users to...

> How does that compare to forcing user to use OSGI??? I am not familiar with either, so I am not sure which is more burdensome I'm not sure either....

It sounds like the easiest to use approach might be something in the middle. 1. Automatically created a snapshot (named, or otherwise) in `InputFormat.getSplits` and make w/e necessary advertisement to...

Sorry, I thought you meant option 1 as the default where they could come back "later" and clean it up -- e.g. some CLI tool. I guess if the Tool...

> If the Accumulo itself supported async callbacks it could make the callbacks immediately when something finished processing. Doesn't Thrift generate async service interfaces (and we just ignore it now)?

That is strange, @risdenk. I'd start with turning on trace logging for the Avatica protocol (see CALCITE-1879 for details). I'd probably take your simple example with Spark here and compare...