-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Present technical conclusions from failed OC project #4815
Present technical conclusions from failed OC project #4815
Conversation
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.
Thanks!
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.
Thanks @arielshaqed for this writeup, it is very helpful!
We assumed multiple non-functional and one functional requirements that did | ||
not actually exist. We should have specified these requirements as part of | ||
the design and communicated them with VE team. | ||
|
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.
I would add here -
The execution plan didn't precede experiments that could have helped us test our main premise quickly. If the main premise is - lakeFS OC is improving Spark write performance to lakeFS, we should start with experiments to test the assumption that we can achieve this main goal. Also, the goals should include concrete performance targets at the first place.
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.
Thanks! Added...
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.
Thanks!
Pulling...
Pulling by force: this is a docs PR and functional tests are not blockers to pulling it. |
Please add more in review!
Closes #4810.