Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Oct 18, 2016

What is this PR for?

When a notebook is created/cloned/imported the title/name of the new notebook should not be duplicate of the existing notebook's title/name

What type of PR is it?

Improvement

Todos

  • Task
    What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-796

How should this be tested?

Create a notebook with name 'Note', Notebook should allow user to create a note
When a user try to create/clone/import a notebook with name 'Note', Notebook should not allow user to create note.
Screenshots (if appropriate)

Screenshot of error message displayed during create/clone notebook
create

Screenshot of error message displayed during import notebook
import

Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

@anthonycorbacho
Copy link
Contributor

I think its okay to have a duplicate name, if the noteId is different nothing bad will happen. What kind of case are you trying to solve here?

@ghost
Copy link
Author

ghost commented Oct 18, 2016

@anthonycorbacho : Lets say if i create a note with name 'Note'. If zeppelin allows me to create a new note with name 'Note', then after sometime when i search for one of this note, I am going to get confused here.

@anthonycorbacho
Copy link
Contributor

I see your point, but let say i want to import a note and i have a note with the same name, it will not allow me to do that and i feel like its a pretty bad user experience here. What do you think?

@ghost
Copy link
Author

ghost commented Oct 26, 2016

@anthonycorbacho : For import note function too, we will have same problem as i pointed out first. Anyway for import note too, any user can give a new name for importing notebook

@ghost
Copy link
Author

ghost commented Oct 26, 2016

@ALL : Please review this PR and let me know your comments

@AhyoungRyu
Copy link
Contributor

@rajarajan-g There are some conflicts in here. Could you handle them? :)

@ghost
Copy link
Author

ghost commented Nov 9, 2016

Ping

@ghost
Copy link
Author

ghost commented Nov 9, 2016

Now i have resolved the conflicts. Please review

@ghost
Copy link
Author

ghost commented Nov 16, 2016

Any updates ?

@Tagar
Copy link
Contributor

Tagar commented Apr 3, 2017

IMHO, automatically adding " (1)", " (2)" .. etc to a note name in case of duplicate name found
might be a better solution than disallowing import at all. A variation on this idea - adding " (import date/time)" suffix to note name would do too (only in case if dup name found).

It'll be then at user's discretion to rename notes appropriately - so they would still be allowed to import a note.

@asfgit asfgit closed this in c38a0a0 May 9, 2018
asfgit pushed a commit that referenced this pull request May 9, 2018
close #83
close #86
close #125
close #133
close #139
close #146
close #193
close #203
close #246
close #262
close #264
close #273
close #291
close #299
close #320
close #347
close #389
close #413
close #423
close #543
close #560
close #658
close #670
close #728
close #765
close #777
close #782
close #783
close #812
close #822
close #841
close #843
close #878
close #884
close #918
close #989
close #1076
close #1135
close #1187
close #1231
close #1304
close #1316
close #1361
close #1385
close #1390
close #1414
close #1422
close #1425
close #1447
close #1458
close #1466
close #1485
close #1492
close #1495
close #1497
close #1536
close #1545
close #1561
close #1577
close #1600
close #1603
close #1678
close #1695
close #1739
close #1748
close #1765
close #1767
close #1776
close #1783
close #1799
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants