[jira] [Updated] (HUDI-2878) Enhance hudi-quick start guide for spark-sql
[ https://issues.apache.org/jira/browse/HUDI-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Xu updated HUDI-2878: - Fix Version/s: 0.10.0 (was: 0.11.0) > Enhance hudi-quick start guide for spark-sql > > > Key: HUDI-2878 > URL: https://issues.apache.org/jira/browse/HUDI-2878 > Project: Apache Hudi > Issue Type: Improvement > Components: Docs >Reporter: sivabalan narayanan >Assignee: Yann Byron >Priority: Major > Labels: pull-request-available > Fix For: 0.10.0 > > > We should try to streamline entire quick start guide using single flow/table > from start to end. As of now, every operations shows 3 to 4 options, but then > when we move to say update, it does not re-use the table from "insert" > section. > > If we look at scala quick start guide, we just use the same table from start > to end. And so, it gives a good end to end run book for users. Where as for > spark-sql, we don't have that now. For instance, if someone wants to try out > delete, they have to create a table by themselves and then go about deleting > based on delete examples given in our quick start guide. > > We need to go over diff ways to do an operation(for eg, create table w/ and > w/o primary keys, etc), but atleast for one table configuration, would be > good to have entire flow covered. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-2878) Enhance hudi-quick start guide for spark-sql
[ https://issues.apache.org/jira/browse/HUDI-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HUDI-2878: - Labels: pull-request-available (was: ) > Enhance hudi-quick start guide for spark-sql > > > Key: HUDI-2878 > URL: https://issues.apache.org/jira/browse/HUDI-2878 > Project: Apache Hudi > Issue Type: Improvement > Components: Docs >Reporter: sivabalan narayanan >Assignee: Yann Byron >Priority: Major > Labels: pull-request-available > Fix For: 0.11.0 > > > We should try to streamline entire quick start guide using single flow/table > from start to end. As of now, every operations shows 3 to 4 options, but then > when we move to say update, it does not re-use the table from "insert" > section. > > If we look at scala quick start guide, we just use the same table from start > to end. And so, it gives a good end to end run book for users. Where as for > spark-sql, we don't have that now. For instance, if someone wants to try out > delete, they have to create a table by themselves and then go about deleting > based on delete examples given in our quick start guide. > > We need to go over diff ways to do an operation(for eg, create table w/ and > w/o primary keys, etc), but atleast for one table configuration, would be > good to have entire flow covered. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-2878) Enhance hudi-quick start guide for spark-sql
[ https://issues.apache.org/jira/browse/HUDI-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sivabalan narayanan updated HUDI-2878: -- Fix Version/s: 0.11.0 > Enhance hudi-quick start guide for spark-sql > > > Key: HUDI-2878 > URL: https://issues.apache.org/jira/browse/HUDI-2878 > Project: Apache Hudi > Issue Type: Improvement > Components: Docs >Reporter: sivabalan narayanan >Priority: Major > Fix For: 0.11.0 > > > We should try to streamline entire quick start guide using single flow/table > from start to end. As of now, every operations shows 3 to 4 options, but then > when we move to say update, it does not re-use the table from "insert" > section. > > If we look at scala quick start guide, we just use the same table from start > to end. And so, it gives a good end to end run book for users. Where as for > spark-sql, we don't have that now. For instance, if someone wants to try out > delete, they have to create a table by themselves and then go about deleting > based on delete examples given in our quick start guide. > > We need to go over diff ways to do an operation(for eg, create table w/ and > w/o primary keys, etc), but atleast for one table configuration, would be > good to have entire flow covered. -- This message was sent by Atlassian Jira (v8.20.1#820001)
