Github user vgromakowski commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/746#issuecomment-188844963
I would suggest to use the same method as for the spark job server,
asynchronous is the default, synchronous is obtain with an additional parameter.
De : Lee moon soo [mailto:notificati...@github.com]
Envoyé : jeudi 25 février 2016 15:48
à : apache/incubator-zeppelin
Cc : GROMAKOWSKI Vincent IST/ISAD
Objet : Re: [incubator-zeppelin] [ZEPPELIN-699] Return Paragraph execution
result for the REST API (#746)
This PR change behavior of REST api job/{notebookId}/{paragraphId} from
asynchronous to synchronous.
To me it's better we keep asynchronous behavior for backward compatibility.
Some user might depends on asynchronous behavior.
Synchronous behavior can be implemented in a different rest api.
â
Reply to this email directly or view it on
GitHub<https://github.com/apache/incubator-zeppelin/pull/746#issuecomment-188816674>.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu
ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
