-
Notifications
You must be signed in to change notification settings - Fork 116
Use configs of previous LogEntry for refresh action #205
Conversation
|
@imback82 What if a user wants to change the configs - with full refresh mode? Should we consider that case also? |
Let's not support it for now (the user can create a new index with a different number of buckets if needed - since refreshing full is like creating a new one). We can introduce a "overwrite" config later if needed. |
imback82
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few minor comments, but the PR looks fine to me.
src/main/scala/com/microsoft/hyperspace/actions/CreateActionBase.scala
Outdated
Show resolved
Hide resolved
src/main/scala/com/microsoft/hyperspace/actions/RefreshActionBase.scala
Outdated
Show resolved
Hide resolved
imback82
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor comment, but LGTM, thanks @sezruby!
What is the context for this pull request?
Fixes #196
What changes were proposed in this pull request?
Instead of using the current spark.config, this PR gets numBuckets and lineage column config from previous index entry at refresh and use it for refresh.
Does this PR introduce any user-facing change?
Fixes a buggy behavior.
How was this patch tested?
Unit test