Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/832
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fea
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/832#issuecomment-209713979
LGTM.
merging if no more comment
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user doanduyhai commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/832#issuecomment-209351550
Ok the CI is green now
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project doe
Github user doanduyhai commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/832#issuecomment-209295518
@felixcheung
Good idea, just re-push with code simplification
---
If your project is set up for it, you can reply to this email and have your
re
Github user doanduyhai commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/832#issuecomment-209238742
@felixcheung
Yes you're right, I'm re-pushing a fix so that on `Note Clone` we're still
using the same paragraphID
---
If your project is set u
GitHub user doanduyhai opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/832
[ZEPPELIN-741] Re-use existing paragraphId on note import
### What is this PR for?
Upon note.json import, do not generate a new paragraphId but re-use the
existing one.
