feat: add Dataframe.cache() factory (no planner handling)#1420
feat: add Dataframe.cache() factory (no planner handling)#1420milenkovicm merged 6 commits intoapache:mainfrom
Dataframe.cache() factory (no planner handling)#1420Conversation
milenkovicm
left a comment
There was a problem hiding this comment.
thanks @killzoner
I have one suggestion
|
no need to implement anything on scheduler side at the moment |
7d48acc to
e76826a
Compare
|
You need to serialise logical plan extension, showcase project https://github.com/milenkovicm/ballista_extensions |
Thanks, I was looking at this part and I was not sure I needed to update ballista proto, this gives more context 🙏 |
fafed16 to
e313d85
Compare
|
I will work on adapting the datafusion example apache/datafusion#19139 with ballista custom query planner once this one is done |
no need to provide ballista planner at the moment, its ok to fail |
4674dc9 to
903d000
Compare
cache() factory
cache() factoryDataframe.cache() factory
Dataframe.cache() factoryDataframe.cache() factory (no planner handling)
903d000 to
d688e14
Compare
milenkovicm
left a comment
There was a problem hiding this comment.
thansk @killzoner few comments and one idea.
what do you think if we add configuration option which would make cache operation a no op instead of throwing exception?
Thanks for the review! All the points make sense to me, putting this to draft and addressing them in the future days |
d688e14 to
6663d84
Compare
|
Updated, this item is still pending though #1420 (comment) |
7e8698a to
90b862a
Compare
|
will review it asap, thanks @killzoner |
milenkovicm
left a comment
There was a problem hiding this comment.
thanks @killzoner just minor comments about tests, otherwise it looks good
08a6a8b to
294e9f1
Compare
294e9f1 to
8f762a8
Compare
Thank you ! I guess there is only #1420 (comment) remaining, but I'm not sure on what to do given the trait API |
thats ok, we can leave it as it is |
| DataFusionError::Internal(format!( | ||
| "Could not deserialize BallistaLogicalPlanNode: {e}" | ||
| )) | ||
| })?; |
|
merging this, thanks @killzoner |
Which issue does this PR close?
Closes #1395 (partially if we want to expand on future configurable cache later).
Rationale for this change
Disable explicitly
cache()method with good user level error rather than relying on currentpanicWhat changes are included in this PR?
CacheFactorywithDataFrame::cachedatafusion#18893)Are there any user-facing changes?
User level error instead of panic