GitHub user masyan opened a pull request:
https://github.com/apache/zeppelin/pull/2038
ZEPPELIN-1999 get interpreter property with replaced context parameters
### What is this PR for?
Adds posibility to use context parameters into property of interpreter.
### What type
Github user masyan closed the pull request at:
https://github.com/apache/zeppelin/pull/2038
---
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
GitHub user masyan opened a pull request:
https://github.com/apache/zeppelin/pull/2046
[ZEPPELIN-1999] get interpreter property with replaced context parameters
### What is this PR for?
Adds posibility to use context parameters (types: String.class,
Double.class, Float.class
Github user masyan closed the pull request at:
https://github.com/apache/zeppelin/pull/2046
---
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
GitHub user masyan opened a pull request:
https://github.com/apache/zeppelin/pull/2047
[ZEPPELIN-1999] get interpreter property with replaced context parameters
### What is this PR for?
Adds posibility to use context parameters (types: String.class,
Double.class, Float.class
Github user masyan closed the pull request at:
https://github.com/apache/zeppelin/pull/2047
---
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
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2078
+1
---
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
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2096
I think this is a good idea. I'm trying to implement this and test task
[#2085](https://github.com/apache/zeppelin/pull/2085)
---
If your project is set up for it, you can reply to this
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2096
@Leemoonsoo
Although probably implement hooks to do this properly. This may confuse the
user. If he is going to register these hooks in their paragraphs, and they will
not work (because they
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2096
@Leemoonsoo
so not working as I expected, method open not runs (in
RemoteInterpreterServer). need to better understand the circuit how it works
---
If your project is set up for it, you can
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2096
close works, but open not. I don't understad why. Maybe run in
if (!lazy.isOpen()) {
lazy.open();
interpreter.interpret(interpetator.getProperty(propert
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2096
and InterpreterContext is unavailable in method close
---
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
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2158
@felixcheung
falls because ";" is delimiter query and after split generated two queries
("/* ", "*/ select ...")
I relied on the standards for SQL89,
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2134
@AhyoungRyu
if you configure the note and working only in report mode then you will not
see when the report is incomplete.I can add the close button
---
If your project is set up for it, you
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2428
we already have a check to limit. setMaxRows duplicate it
---
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
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2731
LGTM
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2761
another interpreters have a version 0.9.0-SNAPSHOT, what problem to update?
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2761
For some reason I thought to the master. LGTM
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2760
@zjffdu
a strange description of PR )
---
GitHub user masyan opened a pull request:
https://github.com/apache/zeppelin/pull/2763
[ZEPPELIN-3194][NEW-INTERPRETER] SAP Universe interpreter
### What is this PR for?
New interpreter, SAP BusinessObjects (Universes). See
[documentation](https://github.com/masyan/zeppelin
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2763
@felixcheung
there are unit tests for convert queries (from Zeppelin format to SAP
format) and unit tests for auto completeion.
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2768
you can reopen PR (for update jenkins status)
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2763
Ready to review
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2782
there is Title of paragraph for that
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2763
@zjffdu @felixcheung
do you have any other questions?
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2763
@Leemoonsoo @felixcheung @zjffdu
if no more questions maybe merge it?
---
Github user masyan closed the pull request at:
https://github.com/apache/zeppelin/pull/2763
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2763
need to specify the format of the "Combined filters (and/or)"
---
GitHub user masyan reopened a pull request:
https://github.com/apache/zeppelin/pull/2763
[ZEPPELIN-3194][NEW-INTERPRETER] SAP Universe interpreter
### What is this PR for?
New interpreter, SAP BusinessObjects (Universes). See
[documentation](https://github.com/masyan/zeppelin
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2763
@Leemoonsoo
okay, I had one question in support of SAP, but they don't answer
---
GitHub user masyan reopened a pull request:
https://github.com/apache/zeppelin/pull/2763
[ZEPPELIN-3194][NEW-INTERPRETER] SAP Universe interpreter
### What is this PR for?
New interpreter, SAP BusinessObjects (Universes). See
[documentation](https://github.com/masyan/zeppelin
Github user masyan closed the pull request at:
https://github.com/apache/zeppelin/pull/2763
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2763
CI green https://travis-ci.org/masyan/zeppelin/builds/342323724
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2763
@Leemoonsoo
found bug of parser
---
Github user masyan closed the pull request at:
https://github.com/apache/zeppelin/pull/2763
---
GitHub user masyan reopened a pull request:
https://github.com/apache/zeppelin/pull/2763
[ZEPPELIN-3194][NEW-INTERPRETER] SAP Universe interpreter
### What is this PR for?
New interpreter, SAP BusinessObjects (Universes). See
[documentation](https://github.com/masyan/zeppelin
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2763
@Leemoonsoo
I fixed the parser. CI red because of unrelated code. Ready to merge
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2830
LGTM
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2828
LGTM
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2763
@Leemoonsoo
https://issues.apache.org/jira/secure/ViewProfile.jspa?name=masyan
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2845
thx. LGTM
---
Github user masyan commented on the issue:
https://github.com/apache/zeppelin/pull/2879
LGTM
---
42 matches
Mail list logo
