Ok, PR for parsing change is sent:
https://github.com/apache/zeppelin/pull/3799
On Tue, Jun 9, 2020 at 8:24 AM Alex Ott wrote:
> Thank you Jeff!
>
> I'll create a ticket, implement it & then rebase my changes on top of it -
> it will simplify the code of my PR as well
>
> On Tue, Jun 9, 2020 at
Thank you Jeff!
I'll create a ticket, implement it & then rebase my changes on top of it -
it will simplify the code of my PR as well
On Tue, Jun 9, 2020 at 12:44 AM Jeff Zhang wrote:
> Hi Alex,
>
> The parsing logic is here, agree that we should put them into
> paragraph local properties and
Hi Alex,
The parsing logic is here, agree that we should put them into
paragraph local properties and improve the parsing logic.
https://github.com/apache/zeppelin/blob/master/zeppelin-zengine/src/main/java/org/apache/zeppelin/notebook/ParagraphTextParser.java
Alex Ott 于2020年6月9日周二 上午12:45写道：
Hi all
related question. I was thinking, maybe I over-complicate the
implementation, and maybe I should use something like this instead:
%cassandra(locale=ruRU, timeFormat="E, d MMM yy", floatPrecision = 5,
outputFormat=cql)
but it's parsed into
'd MMM yy"': 'd MMM yy"', 'floatPrecision': '5',
Hi all
Yesterday I submitted the PR for Cassandra interpreter that introduces the
options for customization of formatting of numbers & time-related types:
https://github.com/apache/zeppelin/pull/3790
And now I'm thinking that such customizations could be useful in other
interpreters as well,
