[jira] [Created] (ZEPPELIN-6021) Spark interpreter

[Ashnee Sharma (Jira)]

Ashnee Sharma created ZEPPELIN-6021:
---

 Summary: Spark interpreter
 Key: ZEPPELIN-6021
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6021
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.11.0, 0.10.1, 0.10.0
 Environment: Test and Prod !image-2024-05-21-21-17-02-102.png!



!image-2024-05-21-21-17-41-751.png!
Reporter: Ashnee Sharma
 Attachments: image-2024-05-21-21-17-02-102.png, 
image-2024-05-21-21-17-41-751.png

I have spark 3.2.0 installed with java 11. While trying to run spark interprter 
in client mode I am getting below error.
org.apache.zeppelin.interpreter.InterpreterException: 
org.apache.zeppelin.interpreter.InterpreterException: Fail to open 
SparkInterpreter at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:76)
 at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:861)
 at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:769)
 at org.apache.zeppelin.scheduler.Job.run(Job.java:186) at 
org.apache.zeppelin.scheduler.AbstractScheduler.runJob(AbstractScheduler.java:135)
 at 
org.apache.zeppelin.scheduler.FIFOScheduler.lambda$runJobInScheduler$0(FIFOScheduler.java:42)
 at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 at java.base/java.lang.Thread.run(Thread.java:829) Caused by: 
org.apache.zeppelin.interpreter.InterpreterException: Fail to open 
SparkInterpreter at 
org.apache.zeppelin.spark.SparkInterpreter.open(SparkInterpreter.java:140) at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(



And When I am trying to in cluster mode for %spark.pyspark
I am getting below error.
org.apache.zeppelin.interpreter.InterpreterException: 
org.apache.zeppelin.interpreter.InterpreterException: Fail to bootstrap pyspark 
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:76)
 at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:861)
 at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:769)
 at org.apache.zeppelin.scheduler.Job.run(Job.java:186) at 
org.apache.zeppelin.scheduler.AbstractScheduler.runJob(AbstractScheduler.java:135)
 at 
org.apache.zeppelin.scheduler.FIFOScheduler.lambda$runJobInScheduler$0(FIFOScheduler.java:42)
 at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 at java.base/java.lang.Thread.run(Thread.java:829) Caused by: 
org.apache.zeppelin.interpreter.InterpreterException: Fail to bootstrap pyspark 
at 
org.apache.zeppelin.spark.PySparkInterpreter.open(PySparkInterpreter.java:103) 
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:70)
 ... 8 more Caused by: java.io.IOException: Fail to run bootstrap script: 
python/zeppelin_pyspark.py
 
 
Fail to execute line 21: from pyspark.conf import SparkConf.
 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-6020) Remove TestUtils class in zeppelin-server

[Philipp Dallig (Jira)]

Philipp Dallig created ZEPPELIN-6020:


 Summary: Remove TestUtils class in zeppelin-server
 Key: ZEPPELIN-6020
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6020
 Project: Zeppelin
  Issue Type: Task
Reporter: Philipp Dallig
Assignee: Philipp Dallig


At the moment we have the TestUtils class in the Zeppelin server modules.
The class is badly named and is not in the main folder. With 
https://github.com/apache/zeppelin/pull/4726 it is possible to remove this 
class completely.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Community over Code EU 2024: The countdown has started!

[Ryan Skraba]

[Note: You're receiving this email because you are subscribed to one
or more project dev@ mailing lists at the Apache Software Foundation.]

We are very close to Community Over Code EU -- check out the amazing
program and the special discounts that we have for you.

Special discounts

You still have the opportunity to secure your ticket for Community
Over Code EU. Explore the various options available, including the
regular pass, the committer and groups pass, and now introducing the
one-day pass tailored for locals in Bratislava.

We also have a special discount for you to attend both Community Over
Code and Berlin Buzzwords from June 9th to 11th. Visit our website to
find out more about this opportunity and contact te...@sg.com.mx to
get the discount code.

Take advantage of the discounts and register now!
https://eu.communityovercode.org/tickets/

Check out the full program!

This year Community Over Code Europe will bring to you three days of
keynotes and sessions that cover topics of interest for ASF projects
and the greater open source ecosystem including data engineering,
performance engineering, search, Internet of Things (IoT) as well as
sessions with tips and lessons learned on building a healthy open
source community.

Check out the program: https://eu.communityovercode.org/program/

Keynote speaker highlights for Community Over Code Europe include:

* Dirk-Willem Van Gulik, VP of Public Policy at the Apache Software
Foundation, will discuss the Cyber Resiliency Act and its impact on
open source (All your code belongs to Policy Makers, Politicians, and
the Law).

* Dr. Sherae Daniel will share the results of her study on the impact
of self-promotion for open source software developers (To Toot or not
to Toot, that is the question).

* Asim Hussain, Executive Director of the Green Software Foundation
will present a framework they have developed for quantifying the
environmental impact of software (Doing for Sustainability what Open
Source did for Software).

* Ruth Ikegah will  discuss the growth of the open source movement in
Africa (From Local Roots to Global Impact: Building an Inclusive Open
Source Community in Africa)

* A discussion panel on EU policies and regulations affecting
specialists working in Open Source Program Offices

Additional activities

* Poster sessions: We invite you to stop by our poster area and see if
the ideas presented ignite a conversation within your team.

* BOF time: Don't miss the opportunity to discuss in person with your
open source colleagues on your shared interests.

* Participants reception: At the end of the first day, we will have a
reception at the event venue. All participants are welcome to attend!

* Spontaneous talks: There is a dedicated room and social space for
having spontaneous talks and sessions. Get ready to share with your
peers.

* Lighting talks: At the end of the event we will have the awaited
Lighting talks, where every participant is welcome to share and
enlighten us.

Please remember:  If you haven't applied for the visa, we will provide
the necessary letter for the process. In the unfortunate case of a
visa rejection, your ticket will be reimbursed.

See you in Bratislava,

Community Over Code EU Team

[jira] [Created] (ZEPPELIN-6019) Remove submarine

[Jongyoul Lee (Jira)]

Jongyoul Lee created ZEPPELIN-6019:
--

 Summary: Remove submarine 
 Key: ZEPPELIN-6019
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6019
 Project: Zeppelin
  Issue Type: Task
Reporter: Jongyoul Lee


https://lists.apache.org/thread/lzh28tn4psfbtp8ooc4ftw3rc9m949cn



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[RESULT] [VOTE] Revert Shell Interpreter

[Jongyoul Lee]

Hello,

The vote for keeping Shell Interpreter for the next release was passed with
9 for +1 (2 binding votes)
1 for 0
1 for -1 (Objection was resolved)

The voting thread.
- https://lists.apache.org/thread/z0ygr40dm5r2syhgo68m6zx0qxkj1o0l

Thank you for your contribution and positive feedback.

I'll make a new minor release including Shell Interpreter again soon.

Best regards,
Jongyoul Lee

Re: [VOTE] Revert Shell Interpreter

[Jongyoul Lee]

Hello,

The vote for keeping Shell Interpreter for the next release was passed with
9 for +1 (2 binding votes)
1 for 0
1 for -1 (Objection was resolved)

The voting thread.
- https://lists.apache.org/thread/z0ygr40dm5r2syhgo68m6zx0qxkj1o0l

Thank you for your contribution and positive feedback.

I'll make a new minor release including Shell Interpreter again soon.

Best regards,
Jongyoul Lee

2024년 5월 12일 (일) 오후 9:44, Jongyoul Lee 님이 작성:

> +1
>
>
> 2024년 4월 30일 (화) 오후 11:45, Jongyoul Lee 님이 작성:
>
>> Hello Nathan,
>>
>> Thank you for the reply. We already talked about what you mentioned in
>> the discussion thread I attached in the first email. Moreover, Zeppelin
>> already provides a way to disable the Shell interpreter so you can disable
>> it even though releases include the Shell interpreter.
>>
>> Best regards,
>> Jongyoul Lee
>>
>> 2024년 4월 30일 (화) 오후 10:52, Rutland, Nathan (CTR) <
>> nathan.rutl...@mail.associates.cisa.dhs.gov>님이 작성:
>>
>>> My reason for removing shell interpreter is that one can easily do:
>>>
>>>
>>>
>>> %sh
>>>
>>> cat /etc/zeppelin/conf/shiro.ini
>>>
>>>
>>>
>>> This would expose all the passwords in a normal system.  I have been
>>> trying to disable sh interpreter ahead of this feature without great
>>> success.
>>>
>>>
>>>
>>> *From:* Jongyoul Lee 
>>> *Sent:* Monday, April 29, 2024 7:30 PM
>>> *To:* Rutland, Nathan (CTR) >> >
>>> *Cc:* dev ; users 
>>> *Subject:* Re: [VOTE] Revert Shell Interpreter
>>>
>>>
>>>
>>> *CAUTION: *This email originated from outside of CISA/DHS. DO NOT click
>>> links or open attachments unless you recognize and/or trust the sender.
>>> Contact your component SOC with questions or concerns.
>>>
>>>
>>>
>>> Hello,
>>>
>>>
>>>
>>> I planed to complete this vote today following general rules for Apache
>>> Zeppelin community history but I prolong this vote to one day more as we
>>> have one veto so that we wait for the reason.
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Jongyoul Lee
>>>
>>>
>>>
>>> 2024년 4월 30일 (화) 오전 9:24, Jongyoul Lee 님이 작성:
>>>
>>> Hello Nathan,
>>>
>>>
>>>
>>> Thank you for interests for this issue.
>>>
>>>
>>>
>>> By the way, I should have explained but all voter who gave -1 need to
>>> leave some comments about why they disagree this vote. It's the voting
>>> policy for all apache projects.[1]
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Jongyoul Lee
>>>
>>>
>>>
>>> [1] https://www.apache.org/foundation/voting.html#Veto
>>> 
>>>
>>>
>>>
>>> 2024년 4월 30일 (화) 오전 2:36, Rutland, Nathan (CTR) <
>>> nathan.rutl...@mail.associates.cisa.dhs.gov>님이 작성:
>>>
>>> -1
>>>
>>>
>>>
>>> *From:* Jongyoul Lee 
>>> *Sent:* Saturday, April 27, 2024 7:21 AM
>>> *To:* users ; dev 
>>> *Subject:* [VOTE] Revert Shell Interpreter
>>>
>>>
>>>
>>> *CAUTION: *This email originated from outside of CISA/DHS. DO NOT click
>>> links or open attachments unless you recognize and/or trust the sender.
>>> Contact your component SOC with questions or concerns.
>>>
>>>
>>>
>>> Hello community,
>>>
>>>
>>>
>>> I propose the vote for reverting Shell interpreter.
>>>
>>>
>>>
>>> Please check the discussion thread[1] before you participate in this
>>> vote.
>>>
>>>
>>>
>>> [] +1 Including Shell interpreter again in the next Zeppelin release
>>>
>>> [] 0 no opinion
>>>
>>> [] -1 Removing Shell interpreter in the next Zeppelin release as it is
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Jongyoul Lee
>>>
>>>
>>>
>>> [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
>>> 
>>>
>>>
>>
>> --
>> Best regards,
>> Jongyoul Lee
>>
>
>
> --
> Best regards,
> Jongyoul Lee
>


-- 
Best regards,
Jongyoul Lee

Re: [VOTE] Revert Shell Interpreter

[Jongyoul Lee]

+1


2024년 4월 30일 (화) 오후 11:45, Jongyoul Lee 님이 작성:

> Hello Nathan,
>
> Thank you for the reply. We already talked about what you mentioned in the
> discussion thread I attached in the first email. Moreover, Zeppelin already
> provides a way to disable the Shell interpreter so you can disable it even
> though releases include the Shell interpreter.
>
> Best regards,
> Jongyoul Lee
>
> 2024년 4월 30일 (화) 오후 10:52, Rutland, Nathan (CTR) <
> nathan.rutl...@mail.associates.cisa.dhs.gov>님이 작성:
>
>> My reason for removing shell interpreter is that one can easily do:
>>
>>
>>
>> %sh
>>
>> cat /etc/zeppelin/conf/shiro.ini
>>
>>
>>
>> This would expose all the passwords in a normal system.  I have been
>> trying to disable sh interpreter ahead of this feature without great
>> success.
>>
>>
>>
>> *From:* Jongyoul Lee 
>> *Sent:* Monday, April 29, 2024 7:30 PM
>> *To:* Rutland, Nathan (CTR) 
>> *Cc:* dev ; users 
>> *Subject:* Re: [VOTE] Revert Shell Interpreter
>>
>>
>>
>> *CAUTION: *This email originated from outside of CISA/DHS. DO NOT click
>> links or open attachments unless you recognize and/or trust the sender.
>> Contact your component SOC with questions or concerns.
>>
>>
>>
>> Hello,
>>
>>
>>
>> I planed to complete this vote today following general rules for Apache
>> Zeppelin community history but I prolong this vote to one day more as we
>> have one veto so that we wait for the reason.
>>
>>
>>
>> Best regards,
>>
>> Jongyoul Lee
>>
>>
>>
>> 2024년 4월 30일 (화) 오전 9:24, Jongyoul Lee 님이 작성:
>>
>> Hello Nathan,
>>
>>
>>
>> Thank you for interests for this issue.
>>
>>
>>
>> By the way, I should have explained but all voter who gave -1 need to
>> leave some comments about why they disagree this vote. It's the voting
>> policy for all apache projects.[1]
>>
>>
>>
>> Best regards,
>>
>> Jongyoul Lee
>>
>>
>>
>> [1] https://www.apache.org/foundation/voting.html#Veto
>> 
>>
>>
>>
>> 2024년 4월 30일 (화) 오전 2:36, Rutland, Nathan (CTR) <
>> nathan.rutl...@mail.associates.cisa.dhs.gov>님이 작성:
>>
>> -1
>>
>>
>>
>> *From:* Jongyoul Lee 
>> *Sent:* Saturday, April 27, 2024 7:21 AM
>> *To:* users ; dev 
>> *Subject:* [VOTE] Revert Shell Interpreter
>>
>>
>>
>> *CAUTION: *This email originated from outside of CISA/DHS. DO NOT click
>> links or open attachments unless you recognize and/or trust the sender.
>> Contact your component SOC with questions or concerns.
>>
>>
>>
>> Hello community,
>>
>>
>>
>> I propose the vote for reverting Shell interpreter.
>>
>>
>>
>> Please check the discussion thread[1] before you participate in this vote.
>>
>>
>>
>> [] +1 Including Shell interpreter again in the next Zeppelin release
>>
>> [] 0 no opinion
>>
>> [] -1 Removing Shell interpreter in the next Zeppelin release as it is
>>
>>
>>
>> Best regards,
>>
>> Jongyoul Lee
>>
>>
>>
>> [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
>> 
>>
>>
>
> --
> Best regards,
> Jongyoul Lee
>


-- 
Best regards,
Jongyoul Lee

Re: [VOTE] Revert Shell Interpreter

[Jongyoul Lee]

Hello Nathan,

Thank you for the reply. We already talked about what you mentioned in the
discussion thread I attached in the first email. Moreover, Zeppelin already
provides a way to disable the Shell interpreter so you can disable it even
though releases include the Shell interpreter.

Best regards,
Jongyoul Lee

2024년 4월 30일 (화) 오후 10:52, Rutland, Nathan (CTR) <
nathan.rutl...@mail.associates.cisa.dhs.gov>님이 작성:

> My reason for removing shell interpreter is that one can easily do:
>
>
>
> %sh
>
> cat /etc/zeppelin/conf/shiro.ini
>
>
>
> This would expose all the passwords in a normal system.  I have been
> trying to disable sh interpreter ahead of this feature without great
> success.
>
>
>
> *From:* Jongyoul Lee 
> *Sent:* Monday, April 29, 2024 7:30 PM
> *To:* Rutland, Nathan (CTR) 
> *Cc:* dev ; users 
> *Subject:* Re: [VOTE] Revert Shell Interpreter
>
>
>
> *CAUTION: *This email originated from outside of CISA/DHS. DO NOT click
> links or open attachments unless you recognize and/or trust the sender.
> Contact your component SOC with questions or concerns.
>
>
>
> Hello,
>
>
>
> I planed to complete this vote today following general rules for Apache
> Zeppelin community history but I prolong this vote to one day more as we
> have one veto so that we wait for the reason.
>
>
>
> Best regards,
>
> Jongyoul Lee
>
>
>
> 2024년 4월 30일 (화) 오전 9:24, Jongyoul Lee 님이 작성:
>
> Hello Nathan,
>
>
>
> Thank you for interests for this issue.
>
>
>
> By the way, I should have explained but all voter who gave -1 need to
> leave some comments about why they disagree this vote. It's the voting
> policy for all apache projects.[1]
>
>
>
> Best regards,
>
> Jongyoul Lee
>
>
>
> [1] https://www.apache.org/foundation/voting.html#Veto
> 
>
>
>
> 2024년 4월 30일 (화) 오전 2:36, Rutland, Nathan (CTR) <
> nathan.rutl...@mail.associates.cisa.dhs.gov>님이 작성:
>
> -1
>
>
>
> *From:* Jongyoul Lee 
> *Sent:* Saturday, April 27, 2024 7:21 AM
> *To:* users ; dev 
> *Subject:* [VOTE] Revert Shell Interpreter
>
>
>
> *CAUTION: *This email originated from outside of CISA/DHS. DO NOT click
> links or open attachments unless you recognize and/or trust the sender.
> Contact your component SOC with questions or concerns.
>
>
>
> Hello community,
>
>
>
> I propose the vote for reverting Shell interpreter.
>
>
>
> Please check the discussion thread[1] before you participate in this vote.
>
>
>
> [] +1 Including Shell interpreter again in the next Zeppelin release
>
> [] 0 no opinion
>
> [] -1 Removing Shell interpreter in the next Zeppelin release as it is
>
>
>
> Best regards,
>
> Jongyoul Lee
>
>
>
> [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
> 
>
>

-- 
Best regards,
Jongyoul Lee

Re: [VOTE] Revert Shell Interpreter

[Jongyoul Lee]

For your information, I used wrong recipients. The previous email is for
users@ and dev@.

Best regards,
Jongyoul Lee


2024년 4월 30일 (화) 오전 9:30, Jongyoul Lee 님이 작성:

> Hello,
>
> I planed to complete this vote today following general rules for Apache
> Zeppelin community history but I prolong this vote to one day more as we
> have one veto so that we wait for the reason.
>
> Best regards,
> Jongyoul Lee
>
> 2024년 4월 30일 (화) 오전 9:24, Jongyoul Lee 님이 작성:
>
>> Hello Nathan,
>>
>> Thank you for interests for this issue.
>>
>> By the way, I should have explained but all voter who gave -1 need to
>> leave some comments about why they disagree this vote. It's the voting
>> policy for all apache projects.[1]
>>
>> Best regards,
>> Jongyoul Lee
>>
>> [1] https://www.apache.org/foundation/voting.html#Veto
>>
>> 2024년 4월 30일 (화) 오전 2:36, Rutland, Nathan (CTR) <
>> nathan.rutl...@mail.associates.cisa.dhs.gov>님이 작성:
>>
>>> -1
>>>
>>>
>>>
>>> *From:* Jongyoul Lee 
>>> *Sent:* Saturday, April 27, 2024 7:21 AM
>>> *To:* users ; dev 
>>> *Subject:* [VOTE] Revert Shell Interpreter
>>>
>>>
>>>
>>> *CAUTION: *This email originated from outside of CISA/DHS. DO NOT click
>>> links or open attachments unless you recognize and/or trust the sender.
>>> Contact your component SOC with questions or concerns.
>>>
>>>
>>>
>>> Hello community,
>>>
>>>
>>>
>>> I propose the vote for reverting Shell interpreter.
>>>
>>>
>>>
>>> Please check the discussion thread[1] before you participate in this
>>> vote.
>>>
>>>
>>>
>>> [] +1 Including Shell interpreter again in the next Zeppelin release
>>>
>>> [] 0 no opinion
>>>
>>> [] -1 Removing Shell interpreter in the next Zeppelin release as it is
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Jongyoul Lee
>>>
>>>
>>>
>>> [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
>>> 
>>>
>>

Re: [VOTE] Revert Shell Interpreter

[Jongyoul Lee]

Hello,

I planed to complete this vote today following general rules for Apache
Zeppelin community history but I prolong this vote to one day more as we
have one veto so that we wait for the reason.

Best regards,
Jongyoul Lee

2024년 4월 30일 (화) 오전 9:24, Jongyoul Lee 님이 작성:

> Hello Nathan,
>
> Thank you for interests for this issue.
>
> By the way, I should have explained but all voter who gave -1 need to
> leave some comments about why they disagree this vote. It's the voting
> policy for all apache projects.[1]
>
> Best regards,
> Jongyoul Lee
>
> [1] https://www.apache.org/foundation/voting.html#Veto
>
> 2024년 4월 30일 (화) 오전 2:36, Rutland, Nathan (CTR) <
> nathan.rutl...@mail.associates.cisa.dhs.gov>님이 작성:
>
>> -1
>>
>>
>>
>> *From:* Jongyoul Lee 
>> *Sent:* Saturday, April 27, 2024 7:21 AM
>> *To:* users ; dev 
>> *Subject:* [VOTE] Revert Shell Interpreter
>>
>>
>>
>> *CAUTION: *This email originated from outside of CISA/DHS. DO NOT click
>> links or open attachments unless you recognize and/or trust the sender.
>> Contact your component SOC with questions or concerns.
>>
>>
>>
>> Hello community,
>>
>>
>>
>> I propose the vote for reverting Shell interpreter.
>>
>>
>>
>> Please check the discussion thread[1] before you participate in this vote.
>>
>>
>>
>> [] +1 Including Shell interpreter again in the next Zeppelin release
>>
>> [] 0 no opinion
>>
>> [] -1 Removing Shell interpreter in the next Zeppelin release as it is
>>
>>
>>
>> Best regards,
>>
>> Jongyoul Lee
>>
>>
>>
>> [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
>> 
>>
>

Re: [VOTE] Revert Shell Interpreter

[Jongyoul Lee]

Hello Nathan,

Thank you for interests for this issue.

By the way, I should have explained but all voter who gave -1 need to leave
some comments about why they disagree this vote. It's the voting policy for
all apache projects.[1]

Best regards,
Jongyoul Lee

[1] https://www.apache.org/foundation/voting.html#Veto

2024년 4월 30일 (화) 오전 2:36, Rutland, Nathan (CTR) <
nathan.rutl...@mail.associates.cisa.dhs.gov>님이 작성:

> -1
>
>
>
> *From:* Jongyoul Lee 
> *Sent:* Saturday, April 27, 2024 7:21 AM
> *To:* users ; dev 
> *Subject:* [VOTE] Revert Shell Interpreter
>
>
>
> *CAUTION: *This email originated from outside of CISA/DHS. DO NOT click
> links or open attachments unless you recognize and/or trust the sender.
> Contact your component SOC with questions or concerns.
>
>
>
> Hello community,
>
>
>
> I propose the vote for reverting Shell interpreter.
>
>
>
> Please check the discussion thread[1] before you participate in this vote.
>
>
>
> [] +1 Including Shell interpreter again in the next Zeppelin release
>
> [] 0 no opinion
>
> [] -1 Removing Shell interpreter in the next Zeppelin release as it is
>
>
>
> Best regards,
>
> Jongyoul Lee
>
>
>
> [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
> 
>

Re: [VOTE] Revert Shell Interpreter

[Bill Brooks]

+1 (non-binding)

Thanks,
Bill

On Sat, Apr 27, 2024 at 5:21 AM Jongyoul Lee  wrote:

> Hello community,
>
> I propose the vote for reverting Shell interpreter.
>
> Please check the discussion thread[1] before you participate in this vote.
>
> [] +1 Including Shell interpreter again in the next Zeppelin release
> [] 0 no opinion
> [] -1 Removing Shell interpreter in the next Zeppelin release as it is
>
> Best regards,
> Jongyoul Lee
>
> [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
>

Re: [VOTE] Revert Shell Interpreter

[Hong]

+1

Thanks for driving!

Hong

> On 28 Apr 2024, at 02:30, Cheng Pan  wrote:
> 
> +1 (non-binding)
> 
> Thanks,
> Cheng Pan
> 
> 
>> On Apr 28, 2024, at 03:45, Danny Cranmer  wrote:
>> 
>> +1
>> 
>> Thanks for driving this
>> 
>> 
>>> On Sat, 27 Apr 2024, 13:57 Jeff Zhang,  wrote:
>>> 
>>> +1
>>> 
 On Sat, Apr 27, 2024 at 8:21 PM Jongyoul Lee  wrote:
>>> 
 Hello community,
 
 I propose the vote for reverting Shell interpreter.
 
 Please check the discussion thread[1] before you participate in this
>>> vote.
 
 [] +1 Including Shell interpreter again in the next Zeppelin release
 [] 0 no opinion
 [] -1 Removing Shell interpreter in the next Zeppelin release as it is
 
 Best regards,
 Jongyoul Lee
 
 [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
 
>>> 
>>> 
>>> --
>>> Best Regards
>>> 
>>> Jeff Zhang
>>> 
> 

[jira] [Created] (ZEPPELIN-6018) Update grpc version in pom.xml for successful Apache Zeppelin build on s390x architecture

[Aditi Sharma (Jira)]

Aditi Sharma created ZEPPELIN-6018:
--

 Summary: Update grpc version in pom.xml for successful Apache 
Zeppelin build on s390x architecture
 Key: ZEPPELIN-6018
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6018
 Project: Zeppelin
  Issue Type: Bug
  Components: build
Affects Versions: 0.11.1, 0.11.0
 Environment: s390x
Reporter: Aditi Sharma


This update changes the grpc-java dependency version in the pom.xml file from 
1.51.0 to 1.62.2. This change ensures compatibility and resolves build issues 
encountered on the s390x architecture. After implementing this change, the 
Apache Zeppelin package now builds successfully on the s390x architecture.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [VOTE] Revert Shell Interpreter

[Cheng Pan]

+1 (non-binding)

Thanks,
Cheng Pan


> On Apr 28, 2024, at 03:45, Danny Cranmer  wrote:
> 
> +1
> 
> Thanks for driving this
> 
> 
> On Sat, 27 Apr 2024, 13:57 Jeff Zhang,  wrote:
> 
>> +1
>> 
>> On Sat, Apr 27, 2024 at 8:21 PM Jongyoul Lee  wrote:
>> 
>>> Hello community,
>>> 
>>> I propose the vote for reverting Shell interpreter.
>>> 
>>> Please check the discussion thread[1] before you participate in this
>> vote.
>>> 
>>> [] +1 Including Shell interpreter again in the next Zeppelin release
>>> [] 0 no opinion
>>> [] -1 Removing Shell interpreter in the next Zeppelin release as it is
>>> 
>>> Best regards,
>>> Jongyoul Lee
>>> 
>>> [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
>>> 
>> 
>> 
>> --
>> Best Regards
>> 
>> Jeff Zhang
>> 

Re: [VOTE] Revert Shell Interpreter

[Danny Cranmer]

+1

Thanks for driving this


On Sat, 27 Apr 2024, 13:57 Jeff Zhang,  wrote:

> +1
>
> On Sat, Apr 27, 2024 at 8:21 PM Jongyoul Lee  wrote:
>
> > Hello community,
> >
> > I propose the vote for reverting Shell interpreter.
> >
> > Please check the discussion thread[1] before you participate in this
> vote.
> >
> > [] +1 Including Shell interpreter again in the next Zeppelin release
> > [] 0 no opinion
> > [] -1 Removing Shell interpreter in the next Zeppelin release as it is
> >
> > Best regards,
> > Jongyoul Lee
> >
> > [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
> >
>
>
> --
> Best Regards
>
> Jeff Zhang
>

Re: [VOTE] Revert Shell Interpreter

[Jeff Zhang]

+1

On Sat, Apr 27, 2024 at 8:21 PM Jongyoul Lee  wrote:

> Hello community,
>
> I propose the vote for reverting Shell interpreter.
>
> Please check the discussion thread[1] before you participate in this vote.
>
> [] +1 Including Shell interpreter again in the next Zeppelin release
> [] 0 no opinion
> [] -1 Removing Shell interpreter in the next Zeppelin release as it is
>
> Best regards,
> Jongyoul Lee
>
> [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
>


-- 
Best Regards

Jeff Zhang

[VOTE] Revert Shell Interpreter

[Jongyoul Lee]

Hello community,

I propose the vote for reverting Shell interpreter.

Please check the discussion thread[1] before you participate in this vote.

[] +1 Including Shell interpreter again in the next Zeppelin release
[] 0 no opinion
[] -1 Removing Shell interpreter in the next Zeppelin release as it is

Best regards,
Jongyoul Lee

[1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn

[jira] [Created] (ZEPPELIN-6017) Revert changes about ZEPPELIN_IDENT_STRING

[Manhua Jiang (Jira)]

Manhua Jiang created ZEPPELIN-6017:
--

 Summary: Revert changes about ZEPPELIN_IDENT_STRING
 Key: ZEPPELIN-6017
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6017
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Manhua Jiang


#5421 delete the definition check about ZEPPELIN_IDENT_STRING in case of 
surefire version upgrade but it will make the log file names become: 

zeppelin--SERVER.log
zeppelin--SERVER.out
zeppelin-interpreter-jdbc-shared_process–SERVER.log

in the defintion of:

zeppelin-${ZEPPELIN_IDENT_STRING}-${HOSTNAME}.log

zeppelin-${ZEPPELIN_IDENT_STRING}-${HOSTNAME}.out

zeppelin-interpreter-%INTERPRETER_ID%-%ZEPPELIN_IDENT_STRING%-%HOSTNAME%.log

 

so, we revert changes about ZEPPELIN_IDENT_STRING



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-6016) Rewrite and enable Livy integration tests

[Cheng Pan (Jira)]

Cheng Pan created ZEPPELIN-6016:
---

 Summary: Rewrite and enable Livy integration tests
 Key: ZEPPELIN-6016
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6016
 Project: Zeppelin
  Issue Type: Test
Reporter: Cheng Pan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-6015) Update GitHub-Actions

[Philipp Dallig (Jira)]

Philipp Dallig created ZEPPELIN-6015:


 Summary: Update GitHub-Actions
 Key: ZEPPELIN-6015
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6015
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Philipp Dallig


The GitHub actions used should be updated to the latest version, as the 
underlying NodeJS is end of life.
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-6014) The Docker image apache/zeppelin:0.11.1 contains macOS metadata for jar files. This leads to a java.util.zip.ZipException: zip END header not found error.

[Antonin Fischer (Jira)]

Antonin Fischer created ZEPPELIN-6014:
-

 Summary: The Docker image apache/zeppelin:0.11.1 contains macOS 
metadata for jar files.  This leads to a java.util.zip.ZipException: zip END 
header not found error.
 Key: ZEPPELIN-6014
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6014
 Project: Zeppelin
  Issue Type: Bug
  Components: zeppelin-integration
Affects Versions: 0.11.1
Reporter: Antonin Fischer


The Docker image {{apache/zeppelin:0.11.1}} contains macOS metadata for jar 
files. This leads to a {{java.util.zip.ZipException: zip END header not found}} 
error in the Spark interpreter due to the inclusion of macOS {{._}} metadata 
files.

Exception:

 
{code:java}
ERROR [2024-04-12 22:50:08,356] (
{FIFOScheduler-interpreter_1585837962-Worker-1}
SparkInterpreter.java[open]:139) - Fail to open SparkInterpreter
scala.reflect.internal.FatalError: Error accessing 
/mnt/disk2/yarn/local/usercache/ondrej.cerny/appcache/application_1711465088664_2677/container_e30_1711465088664_2677_01_01/._spark-scala-2.12-0.11.1.jar
at 
scala.tools.nsc.classpath.AggregateClassPath.$anonfun$list$3(AggregateClassPath.scala:113)
at scala.collection.Iterator.foreach(Iterator.scala:943)
at scala.collection.Iterator.foreach$(Iterator.scala:943)
at scala.collection.AbstractIterator.foreach(Iterator.scala:1431)
at scala.collection.IterableLike.foreach(IterableLike.scala:74)
at scala.collection.IterableLike.foreach$(IterableLike.scala:73)
at scala.collection.AbstractIterable.foreach(Iterable.scala:56)
at 
scala.tools.nsc.classpath.AggregateClassPath.list(AggregateClassPath.scala:101)
at scala.tools.nsc.util.ClassPath.list(ClassPath.scala:36)
at scala.tools.nsc.util.ClassPath.list$(ClassPath.scala:36)
at 
scala.tools.nsc.classpath.AggregateClassPath.list(AggregateClassPath.scala:30)
at 
scala.tools.nsc.symtab.SymbolLoaders$PackageLoader.doComplete(SymbolLoaders.scala:298)
at 
scala.tools.nsc.symtab.SymbolLoaders$SymbolLoader.complete(SymbolLoaders.scala:250)
at scala.reflect.internal.Symbols$Symbol.completeInfo(Symbols.scala:1542)
at scala.reflect.internal.Symbols$Symbol.info(Symbols.scala:1514)
at scala.reflect.internal.Mirrors$RootsBase.init(Mirrors.scala:258)
at scala.tools.nsc.Global.rootMirror$lzycompute(Global.scala:74)
at scala.tools.nsc.Global.rootMirror(Global.scala:72)
at scala.tools.nsc.Global.rootMirror(Global.scala:44)
at 
scala.reflect.internal.Definitions$DefinitionsClass.ObjectClass$lzycompute(Definitions.scala:294)
at 
scala.reflect.internal.Definitions$DefinitionsClass.ObjectClass(Definitions.scala:294)
at 
scala.reflect.internal.Definitions$DefinitionsClass.init(Definitions.scala:1504)
at scala.tools.nsc.Global$Run.(Global.scala:1213)
at scala.tools.nsc.interpreter.IMain._initialize(IMain.scala:124)
at scala.tools.nsc.interpreter.IMain.initializeSynchronous(IMain.scala:146)
at 
org.apache.zeppelin.spark.SparkScala212Interpreter.createSparkILoop(SparkScala212Interpreter.scala:195)
at 
org.apache.zeppelin.spark.AbstractSparkScalaInterpreter.open(AbstractSparkScalaInterpreter.java:116)
at org.apache.zeppelin.spark.SparkInterpreter.open(SparkInterpreter.java:124)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:70)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:861)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:769)
at org.apache.zeppelin.scheduler.Job.run(Job.java:186)
at 
org.apache.zeppelin.scheduler.AbstractScheduler.runJob(AbstractScheduler.java:135)
at 
org.apache.zeppelin.scheduler.FIFOScheduler.lambda$runJobInScheduler$0(FIFOScheduler.java:42)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.io.IOException: Error accessing 
/mnt/disk2/yarn/local/usercache/ondrej.cerny/appcache/application_1711465088664_2677/container_e30_1711465088664_2677_01_01/._spark-scala-2.12-0.11.1.jar
at 
scala.reflect.io.FileZipArchive.scala$reflect$io$FileZipArchive$$openZipFile(ZipArchive.scala:182)
at scala.reflect.io.FileZipArchive.root$lzycompute(ZipArchive.scala:230)
at scala.reflect.io.FileZipArchive.root(ZipArchive.scala:227)
at scala.reflect.io.FileZipArchive.allDirs$lzycompute(ZipArchive.scala:264)
at scala.reflect.io.FileZipArchive.allDirs(ZipArchive.scala:264)
at 
scala.tools.nsc.classpath.ZipArchiveFileLookup.findDirEntry(ZipArchiveFileLookup.scala:76)
at 
scala.tools.nsc.classpath.ZipArchiveFileLookup.list(ZipArchiveFileLookup.scala:63)
at 
scala.tools.nsc.classpath.ZipArchiveFileLookup.list$(ZipArchiveFileLookup.scala:62)
at 

Re: [DISCUSS] Shell interpreter

[Jongyoul Lee]

Hello,

Thank you for your opinion. Almost all opinions show that we'd better keep
Shell interpreter.

Following Apache rule, I'll make a vote in two days. Please leave your
various opinions.

Best regards,
Jongyoul Lee

2024년 4월 15일 (월) 오후 6:59, Danny Cranmer 님이 작성:

> +1 for keeping the interpreter. It poses no additional security risk to any
> interpreter that runs arbitrary code. For instance, it is equivalent to
> running Python subprocess commands (unless I am missing something).
>
> Thanks,
> Danny
>
> On Mon, Apr 15, 2024 at 9:57 AM Cheng Pan  wrote:
>
> > I think the real issue here is that the user is logged in with a normal
> > account, but runs a shell script using the system account, which is an
> > escalation of privileges.
> >
> > Considering the feature has existed for a long period, and the user knows
> > the behavior, it’s good to reserve it as long as there is a clear
> > disclaimer in the docs.
> >
> > I’m +0.5 for keeping it.
> >
> > Thanks,
> > Cheng Pan
> >
> >
> > > On Apr 13, 2024, at 16:04, Manhua Jiang  wrote:
> > >
> > > Hi All,
> > >
> > > I would like to vote keeping it.
> > > Zeppelin offers a way to run script without log in server, and
> > interpreter's permission is controlled.
> > > For the CVE, zeppelin should not make a lot effort to validate whether
> > user's code is safety or not(not only shell, but also all coding
> > interpreter like python,java,scala etc.), but try our best to keep it
> safe,
> > so offering a  server configuration to switch on/off(default to off)
> shell
> > interpreter to end-user should enough for those care about this CVE.
> > >
> > > BTW, share 2 ideas to avoid secure problem:
> > > 1. limited commands like HDFSFileInterpreter
> > > 2. shell interpreter add options to runAs a lower privilege user on
> > demand , and  zeppelin needs to be launched by sudoer
> > >
> > >
> > > On 2024/04/11 09:39:56 Jongyoul Lee wrote:
> > >> Hello,
> > >>
> > >> I want to discuss Shell interpreter issue with you.
> > >>
> > >> For your information, we had a security report using Shell interpreter
> > to
> > >> execute malicious code with a system account. As you know, it's a kind
> > of
> > >> characteristic of Apache Zeppelin but some contributors including me
> > >> thought it was too risky even if it's a feature. Moreover, I thought
> > that
> > >> we had some workarounds to do similar executions.
> > >>
> > >> However, after releasing it, there were many questions via several
> > channels
> > >> about the deprecation of Shell interpreter.
> > >>
> > >> I would like to follow the community's decision. For one more piece of
> > >> information, we already have a security page to warn the code
> execution
> > >> feature so we can keep the Shell interpreter without any further
> > treatment.
> > >>
> > >> Could you please give me your opinion on this?
> > >>
> > >> If we conclude keeping it, I'll release a new release of 0.11.2
> > including
> > >> Shell interpreter again.
> > >>
> > >> Best regards,
> > >> Jongyoul Lee
> > >>
> >
> >
>


-- 
Best regards,
Jongyoul Lee

Re: [DISCUSS] Zeppelin Compatibility/Versioning

[Jongyoul Lee]

Hello,

If I remember correctly, Zeppelin tried to keep backward compatibility for
0.X versions until 0.11.0. We made some break changes on 0.11.0 including
deprecating some interpreters[1] and this Shell interpreter issue.

By the way, we'd better explain which Zeppelin supports the specific
versions of interpreters.

I read the link to Semver and it looks good and like a general idea, so I
would like to follow it up but I want to see others' opinions.

Thank you for the good suggestions.

Best regards,
Jongyoul Lee

[1]
https://cwiki.apache.org/confluence/display/ZEPPELIN/Interpreter+Maintenance

2024년 4월 15일 (월) 오후 7:21, Hong Liang 님이 작성:

> +1 I think it would be good to have a clear expectation around the
> backwards compatibility of upgrades in Zeppelin.
>
> There needs to be some nuance here... Since the functionality surface area
> around interpreters is relatively large, it might be hard to ensure all
> features are available per interpreter, but at the very least, we should
> ensure that within Zeppelin's offering it is backwards compatible!
>
> Regards,
> Hong
>
>
> On 2024/04/15 10:06:42 Danny Cranmer wrote:
> >
> > Hello all,
> > I was reading the shell interpreter thread [1], and it made me wonder
> > about
> > the backwards compatibility guarantees that Zeppelin offers. As a
> > user, I
> > would expect to be able to upgrade from 0.11.0 > 0.11.1 without
> > breaking
> > changes or losing functionality. I would not expect to lose an
> > interpreter.
> >
> > I had a quick look on the dev mailing list and website and cannot
> find
> > anything documenting the version strategy. If it does exist, can you
> > please
> > share the link? If not, I would propose we define a versioning
> strategy
> > that helps users understand compatibility and guarantees, etc. A good
> > place
> > to start is semver [2].
> >
> > I look forward to hearing from the community.
> >
> > Thanks,
> > Danny
> >
> > [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
> > [2] https://semver.org/
> >
>


-- 
Best regards,
Jongyoul Lee

RE: [DISCUSS] Zeppelin Compatibility/Versioning

[Hong Liang]

+1 I think it would be good to have a clear expectation around the
backwards compatibility of upgrades in Zeppelin.

There needs to be some nuance here... Since the functionality surface area
around interpreters is relatively large, it might be hard to ensure all
features are available per interpreter, but at the very least, we should
ensure that within Zeppelin's offering it is backwards compatible!

Regards,
Hong


On 2024/04/15 10:06:42 Danny Cranmer wrote:
>
> Hello all,
> I was reading the shell interpreter thread [1], and it made me wonder
> about
> the backwards compatibility guarantees that Zeppelin offers. As a
> user, I
> would expect to be able to upgrade from 0.11.0 > 0.11.1 without
> breaking
> changes or losing functionality. I would not expect to lose an
> interpreter.
>
> I had a quick look on the dev mailing list and website and cannot find
> anything documenting the version strategy. If it does exist, can you
> please
> share the link? If not, I would propose we define a versioning strategy
> that helps users understand compatibility and guarantees, etc. A good
> place
> to start is semver [2].
>
> I look forward to hearing from the community.
>
> Thanks,
> Danny
>
> [1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
> [2] https://semver.org/
>

[DISCUSS] Zeppelin Compatibility/Versioning

[Danny Cranmer]

Hello all,

I was reading the shell interpreter thread [1], and it made me wonder about
the backwards compatibility guarantees that Zeppelin offers. As a user, I
would expect to be able to upgrade from 0.11.0 > 0.11.1 without breaking
changes or losing functionality. I would not expect to lose an interpreter.

I had a quick look on the dev mailing list and website and cannot find
anything documenting the version strategy. If it does exist, can you please
share the link? If not, I would propose we define a versioning strategy
that helps users understand compatibility and guarantees, etc. A good place
to start is semver [2].

I look forward to hearing from the community.

Thanks,
Danny

[1] https://lists.apache.org/thread/opf3h6b0wc4pnsvqsy0b50vzmozd9qbn
[2] https://semver.org/

Re: [DISCUSS] Shell interpreter

[Danny Cranmer]

+1 for keeping the interpreter. It poses no additional security risk to any
interpreter that runs arbitrary code. For instance, it is equivalent to
running Python subprocess commands (unless I am missing something).

Thanks,
Danny

On Mon, Apr 15, 2024 at 9:57 AM Cheng Pan  wrote:

> I think the real issue here is that the user is logged in with a normal
> account, but runs a shell script using the system account, which is an
> escalation of privileges.
>
> Considering the feature has existed for a long period, and the user knows
> the behavior, it’s good to reserve it as long as there is a clear
> disclaimer in the docs.
>
> I’m +0.5 for keeping it.
>
> Thanks,
> Cheng Pan
>
>
> > On Apr 13, 2024, at 16:04, Manhua Jiang  wrote:
> >
> > Hi All,
> >
> > I would like to vote keeping it.
> > Zeppelin offers a way to run script without log in server, and
> interpreter's permission is controlled.
> > For the CVE, zeppelin should not make a lot effort to validate whether
> user's code is safety or not(not only shell, but also all coding
> interpreter like python,java,scala etc.), but try our best to keep it safe,
> so offering a  server configuration to switch on/off(default to off) shell
> interpreter to end-user should enough for those care about this CVE.
> >
> > BTW, share 2 ideas to avoid secure problem:
> > 1. limited commands like HDFSFileInterpreter
> > 2. shell interpreter add options to runAs a lower privilege user on
> demand , and  zeppelin needs to be launched by sudoer
> >
> >
> > On 2024/04/11 09:39:56 Jongyoul Lee wrote:
> >> Hello,
> >>
> >> I want to discuss Shell interpreter issue with you.
> >>
> >> For your information, we had a security report using Shell interpreter
> to
> >> execute malicious code with a system account. As you know, it's a kind
> of
> >> characteristic of Apache Zeppelin but some contributors including me
> >> thought it was too risky even if it's a feature. Moreover, I thought
> that
> >> we had some workarounds to do similar executions.
> >>
> >> However, after releasing it, there were many questions via several
> channels
> >> about the deprecation of Shell interpreter.
> >>
> >> I would like to follow the community's decision. For one more piece of
> >> information, we already have a security page to warn the code execution
> >> feature so we can keep the Shell interpreter without any further
> treatment.
> >>
> >> Could you please give me your opinion on this?
> >>
> >> If we conclude keeping it, I'll release a new release of 0.11.2
> including
> >> Shell interpreter again.
> >>
> >> Best regards,
> >> Jongyoul Lee
> >>
>
>

Re: [DISCUSS] Shell interpreter

[Cheng Pan]

I think the real issue here is that the user is logged in with a normal 
account, but runs a shell script using the system account, which is an 
escalation of privileges.

Considering the feature has existed for a long period, and the user knows the 
behavior, it’s good to reserve it as long as there is a clear disclaimer in the 
docs.

I’m +0.5 for keeping it.

Thanks,
Cheng Pan


> On Apr 13, 2024, at 16:04, Manhua Jiang  wrote:
> 
> Hi All,
> 
> I would like to vote keeping it.
> Zeppelin offers a way to run script without log in server, and interpreter's 
> permission is controlled.
> For the CVE, zeppelin should not make a lot effort to validate whether user's 
> code is safety or not(not only shell, but also all coding interpreter like 
> python,java,scala etc.), but try our best to keep it safe, so offering a  
> server configuration to switch on/off(default to off) shell interpreter to 
> end-user should enough for those care about this CVE. 
> 
> BTW, share 2 ideas to avoid secure problem:
> 1. limited commands like HDFSFileInterpreter
> 2. shell interpreter add options to runAs a lower privilege user on demand , 
> and  zeppelin needs to be launched by sudoer 
> 
> 
> On 2024/04/11 09:39:56 Jongyoul Lee wrote:
>> Hello,
>> 
>> I want to discuss Shell interpreter issue with you.
>> 
>> For your information, we had a security report using Shell interpreter to
>> execute malicious code with a system account. As you know, it's a kind of
>> characteristic of Apache Zeppelin but some contributors including me
>> thought it was too risky even if it's a feature. Moreover, I thought that
>> we had some workarounds to do similar executions.
>> 
>> However, after releasing it, there were many questions via several channels
>> about the deprecation of Shell interpreter.
>> 
>> I would like to follow the community's decision. For one more piece of
>> information, we already have a security page to warn the code execution
>> feature so we can keep the Shell interpreter without any further treatment.
>> 
>> Could you please give me your opinion on this?
>> 
>> If we conclude keeping it, I'll release a new release of 0.11.2 including
>> Shell interpreter again.
>> 
>> Best regards,
>> Jongyoul Lee
>> 

Re: [DISCUSS] Shell interpreter

[Manhua Jiang]

Hi All,

I would like to vote keeping it.
Zeppelin offers a way to run script without log in server, and interpreter's 
permission is controlled.
For the CVE, zeppelin should not make a lot effort to validate whether user's 
code is safety or not(not only shell, but also all coding interpreter like 
python,java,scala etc.), but try our best to keep it safe, so offering a  
server configuration to switch on/off(default to off) shell interpreter to 
end-user should enough for those care about this CVE. 

BTW, share 2 ideas to avoid secure problem:
1. limited commands like HDFSFileInterpreter
2. shell interpreter add options to runAs a lower privilege user on demand , 
and  zeppelin needs to be launched by sudoer 


On 2024/04/11 09:39:56 Jongyoul Lee wrote:
> Hello,
> 
> I want to discuss Shell interpreter issue with you.
> 
> For your information, we had a security report using Shell interpreter to
> execute malicious code with a system account. As you know, it's a kind of
> characteristic of Apache Zeppelin but some contributors including me
> thought it was too risky even if it's a feature. Moreover, I thought that
> we had some workarounds to do similar executions.
> 
> However, after releasing it, there were many questions via several channels
> about the deprecation of Shell interpreter.
> 
> I would like to follow the community's decision. For one more piece of
> information, we already have a security page to warn the code execution
> feature so we can keep the Shell interpreter without any further treatment.
> 
> Could you please give me your opinion on this?
> 
> If we conclude keeping it, I'll release a new release of 0.11.2 including
> Shell interpreter again.
> 
> Best regards,
> Jongyoul Lee
> 

Re: [DISCUSS] Shell interpreter

[Bill Brooks]

Hello,

I went back and re-read the mailing list summary of CVE-2024-31861 before
composing this message, and I still don't quite grasp what the
reporter/finder of the alleged vulnerability thinks they found. I followed
the links to the NVD at NIST, and didn't find any more substantive
information from the reporter.

The CVE says that the Shell interpreter can be used as "a code generation
gateway", but doesn't say that the Shell interpreter does anything that
enables privilege escalation for any generated code.

Heck, Visual Studio Code allows a programmer to launch a terminal/shell
from within that editor, is that the same thing as "a code generation
gateway"? If we took the assertions here at face value, I think it would be
extraordinarily difficult to write a shell interpreter that could address
the implicit claims made about "Improper Control of Generation of Code"
while still providing the necessary functionality. I guess I'm saying it
would have been great to get more information from the originating reporter
of the alleged vulnerability.

In the absence of more information about what proper control of the code
generation would constitute, I agree with Michiel that we should update the
documentation and republish the shell interpreter.

Bill

On Thu, Apr 11, 2024 at 2:40 AM Jongyoul Lee  wrote:

> Hello,
>
> I want to discuss Shell interpreter issue with you.
>
> For your information, we had a security report using Shell interpreter to
> execute malicious code with a system account. As you know, it's a kind of
> characteristic of Apache Zeppelin but some contributors including me
> thought it was too risky even if it's a feature. Moreover, I thought that
> we had some workarounds to do similar executions.
>
> However, after releasing it, there were many questions via several
> channels about the deprecation of Shell interpreter.
>
> I would like to follow the community's decision. For one more piece of
> information, we already have a security page to warn the code execution
> feature so we can keep the Shell interpreter without any further treatment.
>
> Could you please give me your opinion on this?
>
> If we conclude keeping it, I'll release a new release of 0.11.2 including
> Shell interpreter again.
>
> Best regards,
> Jongyoul Lee
>

[jira] [Created] (ZEPPELIN-6013) Bump some Apache Common Libraries

[Philipp Dallig (Jira)]

Philipp Dallig created ZEPPELIN-6013:


 Summary: Bump some Apache Common Libraries
 Key: ZEPPELIN-6013
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6013
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Philipp Dallig
Assignee: Philipp Dallig


While working on ZEPPELIN-6006 I realized that some libraries of Apache commons 
are outdated. We should update them.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-6012) Rest API call to /api/notebook/job/{jobId} throws NullPointerException

[Shefali Singh (Jira)]

Shefali Singh created ZEPPELIN-6012:
---

 Summary: Rest API call to /api/notebook/job/{jobId} throws 
NullPointerException
 Key: ZEPPELIN-6012
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6012
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.11.0
Reporter: Shefali Singh
 Attachments: image-2024-04-12-15-18-31-283.png

A post request to /api/notebook/job/\{jobId} throws NPE when anything in 
request body is passed, only works when body is empty.

Request body: {}

Response:

java.lang.NullPointerException
        at java.util.HashMap.putMapEntries(HashMap.java:502)
        at java.util.HashMap.putAll(HashMap.java:786)
        at 
org.apache.zeppelin.rest.NotebookRestApi.runNoteJobs(NotebookRestApi.java:829)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at 
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0(ResourceMethodInvocationHandlerFactory.java:52)
        at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:124)
        at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:167)
        at 
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:176)
        at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:79)
        at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:475)
        at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:397)
        at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:81)
        at 
org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:255)

 

Does passing a request body to this endpoint not supported in 0.11.0? Doesn't 
throw any error in 0.10.1



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[DISCUSS] Shell interpreter

[Jongyoul Lee]

Hello,

I want to discuss Shell interpreter issue with you.

For your information, we had a security report using Shell interpreter to
execute malicious code with a system account. As you know, it's a kind of
characteristic of Apache Zeppelin but some contributors including me
thought it was too risky even if it's a feature. Moreover, I thought that
we had some workarounds to do similar executions.

However, after releasing it, there were many questions via several channels
about the deprecation of Shell interpreter.

I would like to follow the community's decision. For one more piece of
information, we already have a security page to warn the code execution
feature so we can keep the Shell interpreter without any further treatment.

Could you please give me your opinion on this?

If we conclude keeping it, I'll release a new release of 0.11.2 including
Shell interpreter again.

Best regards,
Jongyoul Lee

Re: [ANNOUNCE] Apache Zeppelin 0.11.1 available

[Manhua Jiang]

Hi, the released package contains a lot hidden files and interferes classLoader 
to load jars like:
(downloaded from 
https://dist.apache.org/repos/dist/release/zeppelin/zeppelin-0.11.1/ )
```
 INFO [2024-04-10 16:16:12,133] ({ParallelScheduler-Worker-1} 
SparkInterpreter.java[extractScalaVersion]:272) - Using Scala: 2.12
 INFO [2024-04-10 16:16:12,174] ({ParallelScheduler-Worker-1} 
SparkScala212Interpreter.scala[createSparkILoop]:170) - Scala shell repl output 
dir: /tmp/spark3677241664930357308
 INFO [2024-04-10 16:16:12,439] ({ParallelScheduler-Worker-1} 
SparkScala212Interpreter.scala[createSparkILoop]:179) - UserJars: 
file:/data/soft/zeppelin-0.11.1-bin-all/interpreter/spark/spark-interpreter-0.11.1.jar:/data/soft/zeppelin/interpreter/spark/scala-2.12/._spark-scala-2.12-0.11.1.jar:/data/soft/zeppelin/interpreter/spark/scala-2.12/spark-scala-2.12-0.11.1.jar
ERROR [2024-04-10 16:16:13,361] ({ParallelScheduler-Worker-1} 
SparkInterpreter.java[open]:139) - Fail to open SparkInterpreter
scala.reflect.internal.FatalError: Error accessing 
/data/soft/zeppelin/interpreter/spark/._spark-interpreter-0.11.1.jar
at 
scala.tools.nsc.classpath.AggregateClassPath.$anonfun$list$3(AggregateClassPath.scala:113)
at scala.collection.Iterator.foreach(Iterator.scala:943)
at scala.collection.Iterator.foreach$(Iterator.scala:943)
at scala.collection.AbstractIterator.foreach(Iterator.scala:1431)
at scala.collection.IterableLike.foreach(IterableLike.scala:74)
at scala.collection.IterableLike.foreach$(IterableLike.scala:73)
at scala.collection.AbstractIterable.foreach(Iterable.scala:56)
at 
scala.tools.nsc.classpath.AggregateClassPath.list(AggregateClassPath.scala:101)
at scala.tools.nsc.util.ClassPath.list(ClassPath.scala:36)
at scala.tools.nsc.util.ClassPath.list$(ClassPath.scala:36)
at 
scala.tools.nsc.classpath.AggregateClassPath.list(AggregateClassPath.scala:30)
at 
scala.tools.nsc.symtab.SymbolLoaders$PackageLoader.doComplete(SymbolLoaders.scala:298)
at 
scala.tools.nsc.symtab.SymbolLoaders$SymbolLoader.complete(SymbolLoaders.scala:250)
at 
scala.reflect.internal.Symbols$Symbol.completeInfo(Symbols.scala:1542)
at scala.reflect.internal.Symbols$Symbol.info(Symbols.scala:1514)
at scala.reflect.internal.Mirrors$RootsBase.init(Mirrors.scala:258)
at scala.tools.nsc.Global.rootMirror$lzycompute(Global.scala:74)
at scala.tools.nsc.Global.rootMirror(Global.scala:72)
at scala.tools.nsc.util.ClassPath.list(ClassPath.scala:36)
at scala.tools.nsc.util.ClassPath.list$(ClassPath.scala:36)
at 
scala.tools.nsc.classpath.AggregateClassPath.list(AggregateClassPath.scala:30)
at 
scala.tools.nsc.symtab.SymbolLoaders$PackageLoader.doComplete(SymbolLoaders.scala:298)
at 
scala.tools.nsc.symtab.SymbolLoaders$SymbolLoader.complete(SymbolLoaders.scala:250)
at 
scala.reflect.internal.Symbols$Symbol.completeInfo(Symbols.scala:1542)
at scala.reflect.internal.Symbols$Symbol.info(Symbols.scala:1514)
at scala.reflect.internal.Mirrors$RootsBase.init(Mirrors.scala:258)
at scala.tools.nsc.Global.rootMirror$lzycompute(Global.scala:74)
at scala.tools.nsc.Global.rootMirror(Global.scala:72)
at scala.tools.nsc.Global.rootMirror(Global.scala:44)
at 
scala.reflect.internal.Definitions$DefinitionsClass.ObjectClass$lzycompute(Definitions.scala:301)
at 
scala.reflect.internal.Definitions$DefinitionsClass.ObjectClass(Definitions.scala:301)
at 
scala.reflect.internal.Definitions$DefinitionsClass.init(Definitions.scala:1511)
at scala.tools.nsc.Global$Run.(Global.scala:1213)
at scala.tools.nsc.interpreter.IMain._initialize(IMain.scala:124)
at 
scala.tools.nsc.interpreter.IMain.initializeSynchronous(IMain.scala:146)
at 
org.apache.zeppelin.spark.SparkScala212Interpreter.createSparkILoop(SparkScala212Interpreter.scala:195)
at 
org.apache.zeppelin.spark.AbstractSparkScalaInterpreter.open(AbstractSparkScalaInterpreter.java:116)
at 
org.apache.zeppelin.spark.SparkInterpreter.open(SparkInterpreter.java:124)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:70)
at 
org.apache.zeppelin.interpreter.Interpreter.getInterpreterInTheSameSessionByClassName(Interpreter.java:322)
at 
org.apache.zeppelin.interpreter.Interpreter.getInterpreterInTheSameSessionByClassName(Interpreter.java:333)
at 
org.apache.zeppelin.spark.SparkSqlInterpreter.open(SparkSqlInterpreter.java:57)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:70)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:861)
at 

[jira] [Created] (ZEPPELIN-6011) Update JAVA_HOME environment variable to openjdk11

[Gayle Tan (Jira)]

Gayle Tan created ZEPPELIN-6011:
---

 Summary: Update JAVA_HOME environment variable to openjdk11
 Key: ZEPPELIN-6011
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6011
 Project: Zeppelin
  Issue Type: Bug
Reporter: Gayle Tan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-6010) Compilation error from source code package version zeppelin-0.11.1

[Yu Hou (Jira)]

Yu Hou created ZEPPELIN-6010:


 Summary: Compilation error from source code package version 
zeppelin-0.11.1
 Key: ZEPPELIN-6010
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6010
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.11.1
 Environment: centos7-x86_64
zeppelin-0.11.1
Reporter: Yu Hou
 Attachments: image-2024-04-08-09-35-55-685.png, 
image-2024-04-08-09-36-19-574.png

When I compile from 
{code:java}https://archive.apache.org/dist/zeppelin/zeppelin-0.11.1/zeppelin-0.11.1.tgz
 {code} The following error occurred while downloading the source code package,
 !image-2024-04-08-09-35-55-685.png! 

 and when I used it 
 {code:java} https://github.com/apache/zeppelin/tree/v0.11.1  {code}
 There was no such error during compilation, so I suspect there may be an issue 
with the source code package of the distribution. 
 !image-2024-04-08-09-36-19-574.png! 

Please help me take a look at this issue.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Community over Code EU 2024: Start planning your trip!

[Ryan Skraba]

[Note: You're receiving this email because you are subscribed to one
or more project dev@ mailing lists at the Apache Software Foundation.]

Dear community,

We hope you are doing great, are you ready for Community Over Code EU?
Check out the featured sessions, get your tickets with special
discounts and start planning your trip.

Save your spot! Take a look at our lineup of sessions, panelists and
featured speakers and make your final choice:

* EU policies and regulations affecting open source specialists working in OSPOs

The panel will discuss how EU legislation affects the daily work of
open source operations. Panelists will cover some recent policy
updates, the challenges of staying compliant when managing open source
contribution and usage within organizations, and their personal
experiences in adapting to the changing European regulatory
environment.

* Doing for sustainability, what open source did for software

In this keynote Asim Hussain will explain the history of Impact
Framework, a coalition of hundreds of software practitioners with
tangible solutions that directly foster meaningful change by measuring
the environmental impacts of a piece of software.

Don’t forget that we have special discounts for groups, students and
Apache committers. Visit the website to discover more about these
rates.[1]

It's time for you to start planning your trip. Remember that we have
prepared a “How to get there” guide that will be helpful to find out
the best transportation, either train, bus, flight or boat to
Bratislava from wherever you are coming from. Take a look at the
different options and please reach out to us if you have any
questions.

We have available rooms -with a special rate- at the Radisson Blu
Carlton Hotel, where the event will take place and at the Park Inn
Hotel which is only 5 minutes walking from the venue. [2] However, you
are free to choose any other accommodation options around the city.

See you in Bratislava,
Community Over Code EU Team

[1]: https://eu.communityovercode.org/tickets/ "Register"
[2]: https://eu.communityovercode.org/venue/ "Where to stay"

Re: [ANNOUNCE] Apache Zeppelin 0.11.1 available

[Jongyoul Lee]

Hello,

The docker image became normal.

We can use the docker image.

Best regards,
Jongyoul Lee

2024년 4월 2일 (화) 오전 11:18, Jongyoul Lee 님이 작성:
>
> Hello,
>
> We have a problem with a docker image for the new release.
>
> I'm checking it and get back to you after solving the issue.
>
> Best regards,
> Jongyoul
>
> 2024년 4월 2일 (화) 오전 2:08, Jongyoul Lee 님이 작성:
> >
> > We are happy to announce the availability of Zeppelin 0.11.1!
> >
> >
> >
> > Zeppelin 0.11.1 is a maintenance release containing security fixes. This
> >
> > release is based on the branch-0.11 maintenance branch of Zeppelin. We 
> > strongly
> >
> > recommend all 0.11.0 users to upgrade to this stable release.
> >
> >
> >
> > To download Zeppelin 0.11.1, head over to the download page:
> >
> > https://zeppelin.apache.org/download.html
> >
> >
> >
> > To view the release notes:
> >
> > https://zeppelin.apache.org/releases/zeppelin-release-0.11.1.html
> >
> >
> >
> > We would like to acknowledge all community members for contributing to this
> >
> > release. This release would not have been possible without you.
> >
> >
> >
> > Jongyoul Lee
>
>
>
> --
> Best regards,
> Jongyoul Lee



-- 
Best regards,
Jongyoul Lee

Participate in the ASF 25th Anniversary Campaign

[Brian Proffitt]

Hi everyone,

As part of The ASF’s 25th anniversary campaign[1], we will be celebrating
projects and communities in multiple ways.

We invite all projects and contributors to participate in the following
ways:

* Individuals - submit your first contribution:
https://news.apache.org/foundation/entry/the-asf-launches-firstasfcontribution-campaign
* Projects - share your public good story:
https://docs.google.com/forms/d/1vuN-tUnBwpTgOE5xj3Z5AG1hsOoDNLBmGIqQHwQT6k8/viewform?edit_requested=true
* Projects - submit a project spotlight for the blog:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=278466116
* Projects - contact the Voice of Apache podcast (formerly Feathercast) to
be featured: https://feathercast.apache.org/help/
*  Projects - use the 25th anniversary template and the #ASF25Years hashtag
on social media:
https://docs.google.com/presentation/d/1oDbMol3F_XQuCmttPYxBIOIjRuRBksUjDApjd8Ve3L8/edit#slide=id.g26b0919956e_0_13

If you have questions, email the Marketing & Publicity team at
mark...@apache.org.

Peace,
BKP

[1] https://apache.org/asf25years/

[NOTE: You are receiving this message because you are a contributor to an
Apache Software Foundation project. The ASF will very occasionally send out
messages relating to the Foundation to contributors and members, such as
this one.]

Brian Proffitt
VP, Marketing & Publicity
VP, Conferences

[jira] [Created] (ZEPPELIN-6009) Remove Shell interpreter and its tests

[Jongyoul Lee (Jira)]

Jongyoul Lee created ZEPPELIN-6009:
--

 Summary: Remove Shell interpreter and its tests
 Key: ZEPPELIN-6009
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6009
 Project: Zeppelin
  Issue Type: Task
  Components: Interpreters, shell
Reporter: Jongyoul Lee
Assignee: Jongyoul Lee






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [ANNOUNCE] Apache Zeppelin 0.11.1 available

[Jongyoul Lee]

Hello,

We have a problem with a docker image for the new release.

I'm checking it and get back to you after solving the issue.

Best regards,
Jongyoul

2024년 4월 2일 (화) 오전 2:08, Jongyoul Lee 님이 작성:
>
> We are happy to announce the availability of Zeppelin 0.11.1!
>
>
>
> Zeppelin 0.11.1 is a maintenance release containing security fixes. This
>
> release is based on the branch-0.11 maintenance branch of Zeppelin. We 
> strongly
>
> recommend all 0.11.0 users to upgrade to this stable release.
>
>
>
> To download Zeppelin 0.11.1, head over to the download page:
>
> https://zeppelin.apache.org/download.html
>
>
>
> To view the release notes:
>
> https://zeppelin.apache.org/releases/zeppelin-release-0.11.1.html
>
>
>
> We would like to acknowledge all community members for contributing to this
>
> release. This release would not have been possible without you.
>
>
>
> Jongyoul Lee



-- 
Best regards,
Jongyoul Lee

[ANNOUNCE] Apache Zeppelin 0.11.1 available

[Jongyoul Lee]

We are happy to announce the availability of Zeppelin 0.11.1!



Zeppelin 0.11.1 is a maintenance release containing security fixes. This

release is based on the branch-0.11 maintenance branch of Zeppelin. We
strongly

recommend all 0.11.0 users to upgrade to this stable release.



To download Zeppelin 0.11.1, head over to the download page:

https://zeppelin.apache.org/download.html



To view the release notes:

https://zeppelin.apache.org/releases/zeppelin-release-0.11.1.html



We would like to acknowledge all community members for contributing to this

release. This release would not have been possible without you.



Jongyoul Lee

[RESULT] [VOTE] Release Apache Zeppelin 0.11.1 (RC1)

[Jongyoul Lee]

The vote passes with 3 binding +1 votes, 2 non-binding +1 votes, and
no +0 or -1 votes. Thanks for everyone who verified rc and voted.

+1:
Anthony Corbacho*

Cheng Pan

Jeff Zhang*
Jongyoul Lee*

Michael Matsko

+0:

-1:

*binding

Vote thread:

https://lists.apache.org/thread/2vw584n2kowt751h8nlob8r4b1h8gtm4


Best regards,

Jongyoul Lee

[jira] [Created] (ZEPPELIN-6008) Pin plotly 5.19.0

[Cheng Pan (Jira)]

Cheng Pan created ZEPPELIN-6008:
---

 Summary: Pin plotly 5.19.0
 Key: ZEPPELIN-6008
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6008
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Cheng Pan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [EXTERNAL] Re: [VOTE] Release Apache Zeppelin 0.11.1 (RC1)

[Anthony Corbacho]

+1

On Sat, Mar 30, 2024 at 11:54 PM Jeff Zhang  wrote:

> +1, thanks for your effort, Jongyoul
>
> On Sat, Mar 30, 2024 at 12:41 AM Matsko, Michael <
> michaelmat...@maximus.com>
> wrote:
>
> > +1
> >
> > Michael Matsko
> > Senior Specialist
> > M: 703-516-9789
> > E: michaelmat...@maximus.com
> >
> >
> > 1600 Tysons Blvd, Suite 1400 | McLean | Virginia | 22102-4865
> >
> > -Original Message-
> > From: Cheng Pan 
> > Sent: Friday, March 29, 2024 5:00 AM
> > To: dev@zeppelin.apache.org
> > Subject: [EXTERNAL] Re: [VOTE] Release Apache Zeppelin 0.11.1 (RC1)
> >
> > +1 (non-binding), thanks for making this patched release.
> >
> > I checked:
> >
> > - the versions listed in `conf/interpreter-list` are correct
> > - artifacts' signatures are good
> > - all links in the mail are valid and look good, except for the RELEASE
> > NOTE, which does not match the real changes.
> > - I checked the GHA CI results, some tests failed but should not be
> > blocker issue
> >
> > Thanks,
> > Cheng Pan
> >
> >
> > > On Mar 29, 2024, at 16:50, Jongyoul Lee  wrote:
> > >
> > > Hell forks,
> > >
> > > I missed the due date.
> > >
> > > This vote will close at 2 AM on 2nd Apr PDT.
> > >
> > > Best regards,
> > > Jongyoul Lee
> > >
> > > 2024년 3월 29일 (금) 오후 5:47, Jongyoul Lee 님이 작성:
> > >
> > >> Hello,
> > >>
> > >> +1
> > >>
> > >> Best regards,
> > >> Jongyoul Lee
> > >>
> > >> 2024년 3월 29일 (금) 오후 5:30, Jongyoul Lee 님이 작성:
> > >>
> > >>> Hi folks,
> > >>>
> > >>> I propose the following RC to be released for the Apache Zeppelin
> > >>> 0.11.1 release.
> > >>>
> > >>>
> > >>> The commit id is 9a51785a3a86d93888a0d959815b097ba41b35d5 :
> > >>> https://github.com/apache/zeppelin/commit/9a51785a3a86d93888a0d95981
> > >>> 5b097ba41b35d5
> > >>>
> > >>> This corresponds to the tag: v0.11.1-rc1 :
> > >>> https://github.com/apache/zeppelin/releases/tag/v0.11.1-rc1
> > >>>
> > >>> The release archives (tgz), signature, and checksums are here
> > >>> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.11.1-rc1/
> > >>>
> > >>> The release candidate consists of the following source distribution
> > >>> archive zeppelin-0.11.1.tgz
> > >>>
> > >>> In addition, the following supplementary binary distributions are
> > >>> provided for user convenience at the same location
> > >>> zeppelin-0.11.1-bin-all.tgz
> > >>>
> > >>>
> > >>> The maven artifacts are here
> > >>>
> > >>> https://repository.apache.org/content/repositories/orgapachezeppelin
> > >>> -1336/org/apache/zeppelin/
> > >>>
> > >>> You can find the KEYS file here:
> > >>> https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > >>>
> > >>> Release notes available at
> > >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=123
> > >>> 16221=12354214
> > >>>
> > >>>
> > >>> For more information, this release has security fixes mostly.
> > >>>
> > >>> Vote will be open for next 72 hours (close at 7am 8/Nov PDT).
> > >>>
> > >>> [ ] +1 approve
> > >>> [ ] 0 no opinion
> > >>> [ ] -1 disapprove (and reason why)
> > >>>
> > >>>
> > >>
> > >> --
> > >> 이종열, Jongyoul Lee, 李宗烈
> > >> http://madeng.net
> > >>
> > >
> > >
> > > --
> > > 이종열, Jongyoul Lee, 李宗烈
> > > http://madeng.net
> >
> > CONFIDENTIALITY NOTICE: This e-mail, including attachments, is for the
> > sole use of the intended recipient(s) and may contain confidential and
> > privileged information or otherwise be protected by law. Any unauthorized
> > review, use, disclosure or distribution is prohibited. If you are not the
> > intended recipient, please contact the sender and destroy all copies and
> > the original message.
> >
>
>
> --
> Best Regards
>
> Jeff Zhang
>

Re: [EXTERNAL] Re: [VOTE] Release Apache Zeppelin 0.11.1 (RC1)

[Jeff Zhang]

+1, thanks for your effort, Jongyoul

On Sat, Mar 30, 2024 at 12:41 AM Matsko, Michael 
wrote:

> +1
>
> Michael Matsko
> Senior Specialist
> M: 703-516-9789
> E: michaelmat...@maximus.com
>
>
> 1600 Tysons Blvd, Suite 1400 | McLean | Virginia | 22102-4865
>
> -Original Message-
> From: Cheng Pan 
> Sent: Friday, March 29, 2024 5:00 AM
> To: dev@zeppelin.apache.org
> Subject: [EXTERNAL] Re: [VOTE] Release Apache Zeppelin 0.11.1 (RC1)
>
> +1 (non-binding), thanks for making this patched release.
>
> I checked:
>
> - the versions listed in `conf/interpreter-list` are correct
> - artifacts' signatures are good
> - all links in the mail are valid and look good, except for the RELEASE
> NOTE, which does not match the real changes.
> - I checked the GHA CI results, some tests failed but should not be
> blocker issue
>
> Thanks,
> Cheng Pan
>
>
> > On Mar 29, 2024, at 16:50, Jongyoul Lee  wrote:
> >
> > Hell forks,
> >
> > I missed the due date.
> >
> > This vote will close at 2 AM on 2nd Apr PDT.
> >
> > Best regards,
> > Jongyoul Lee
> >
> > 2024년 3월 29일 (금) 오후 5:47, Jongyoul Lee 님이 작성:
> >
> >> Hello,
> >>
> >> +1
> >>
> >> Best regards,
> >> Jongyoul Lee
> >>
> >> 2024년 3월 29일 (금) 오후 5:30, Jongyoul Lee 님이 작성:
> >>
> >>> Hi folks,
> >>>
> >>> I propose the following RC to be released for the Apache Zeppelin
> >>> 0.11.1 release.
> >>>
> >>>
> >>> The commit id is 9a51785a3a86d93888a0d959815b097ba41b35d5 :
> >>> https://github.com/apache/zeppelin/commit/9a51785a3a86d93888a0d95981
> >>> 5b097ba41b35d5
> >>>
> >>> This corresponds to the tag: v0.11.1-rc1 :
> >>> https://github.com/apache/zeppelin/releases/tag/v0.11.1-rc1
> >>>
> >>> The release archives (tgz), signature, and checksums are here
> >>> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.11.1-rc1/
> >>>
> >>> The release candidate consists of the following source distribution
> >>> archive zeppelin-0.11.1.tgz
> >>>
> >>> In addition, the following supplementary binary distributions are
> >>> provided for user convenience at the same location
> >>> zeppelin-0.11.1-bin-all.tgz
> >>>
> >>>
> >>> The maven artifacts are here
> >>>
> >>> https://repository.apache.org/content/repositories/orgapachezeppelin
> >>> -1336/org/apache/zeppelin/
> >>>
> >>> You can find the KEYS file here:
> >>> https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> >>>
> >>> Release notes available at
> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=123
> >>> 16221=12354214
> >>>
> >>>
> >>> For more information, this release has security fixes mostly.
> >>>
> >>> Vote will be open for next 72 hours (close at 7am 8/Nov PDT).
> >>>
> >>> [ ] +1 approve
> >>> [ ] 0 no opinion
> >>> [ ] -1 disapprove (and reason why)
> >>>
> >>>
> >>
> >> --
> >> 이종열, Jongyoul Lee, 李宗烈
> >> http://madeng.net
> >>
> >
> >
> > --
> > 이종열, Jongyoul Lee, 李宗烈
> > http://madeng.net
>
> CONFIDENTIALITY NOTICE: This e-mail, including attachments, is for the
> sole use of the intended recipient(s) and may contain confidential and
> privileged information or otherwise be protected by law. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not the
> intended recipient, please contact the sender and destroy all copies and
> the original message.
>


-- 
Best Regards

Jeff Zhang

RE: [EXTERNAL] Re: [VOTE] Release Apache Zeppelin 0.11.1 (RC1)

[Matsko, Michael]

+1

Michael Matsko
Senior Specialist
M: 703-516-9789
E: michaelmat...@maximus.com


1600 Tysons Blvd, Suite 1400 | McLean | Virginia | 22102-4865

-Original Message-
From: Cheng Pan 
Sent: Friday, March 29, 2024 5:00 AM
To: dev@zeppelin.apache.org
Subject: [EXTERNAL] Re: [VOTE] Release Apache Zeppelin 0.11.1 (RC1)

+1 (non-binding), thanks for making this patched release.

I checked:

- the versions listed in `conf/interpreter-list` are correct
- artifacts' signatures are good
- all links in the mail are valid and look good, except for the RELEASE NOTE, 
which does not match the real changes.
- I checked the GHA CI results, some tests failed but should not be blocker 
issue

Thanks,
Cheng Pan


> On Mar 29, 2024, at 16:50, Jongyoul Lee  wrote:
>
> Hell forks,
>
> I missed the due date.
>
> This vote will close at 2 AM on 2nd Apr PDT.
>
> Best regards,
> Jongyoul Lee
>
> 2024년 3월 29일 (금) 오후 5:47, Jongyoul Lee 님이 작성:
>
>> Hello,
>>
>> +1
>>
>> Best regards,
>> Jongyoul Lee
>>
>> 2024년 3월 29일 (금) 오후 5:30, Jongyoul Lee 님이 작성:
>>
>>> Hi folks,
>>>
>>> I propose the following RC to be released for the Apache Zeppelin
>>> 0.11.1 release.
>>>
>>>
>>> The commit id is 9a51785a3a86d93888a0d959815b097ba41b35d5 :
>>> https://github.com/apache/zeppelin/commit/9a51785a3a86d93888a0d95981
>>> 5b097ba41b35d5
>>>
>>> This corresponds to the tag: v0.11.1-rc1 :
>>> https://github.com/apache/zeppelin/releases/tag/v0.11.1-rc1
>>>
>>> The release archives (tgz), signature, and checksums are here
>>> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.11.1-rc1/
>>>
>>> The release candidate consists of the following source distribution
>>> archive zeppelin-0.11.1.tgz
>>>
>>> In addition, the following supplementary binary distributions are
>>> provided for user convenience at the same location
>>> zeppelin-0.11.1-bin-all.tgz
>>>
>>>
>>> The maven artifacts are here
>>>
>>> https://repository.apache.org/content/repositories/orgapachezeppelin
>>> -1336/org/apache/zeppelin/
>>>
>>> You can find the KEYS file here:
>>> https://dist.apache.org/repos/dist/release/zeppelin/KEYS
>>>
>>> Release notes available at
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=123
>>> 16221=12354214
>>>
>>>
>>> For more information, this release has security fixes mostly.
>>>
>>> Vote will be open for next 72 hours (close at 7am 8/Nov PDT).
>>>
>>> [ ] +1 approve
>>> [ ] 0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>>
>>
>> --
>> 이종열, Jongyoul Lee, 李宗烈
>> http://madeng.net
>>
>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net

CONFIDENTIALITY NOTICE: This e-mail, including attachments, is for the sole use 
of the intended recipient(s) and may contain confidential and privileged 
information or otherwise be protected by law. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender and destroy all copies and the original 
message.

[jira] [Created] (ZEPPELIN-6007) Enhance release scripts for tar shasum commands detection

[Cheng Pan (Jira)]

Cheng Pan created ZEPPELIN-6007:
---

 Summary: Enhance release scripts for tar shasum commands detection
 Key: ZEPPELIN-6007
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6007
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Cheng Pan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [VOTE] Release Apache Zeppelin 0.11.1 (RC1)

[Cheng Pan]

+1 (non-binding), thanks for making this patched release.

I checked:

- the versions listed in `conf/interpreter-list` are correct
- artifacts' signatures are good
- all links in the mail are valid and look good, except for the RELEASE NOTE, 
which does not match the real changes.
- I checked the GHA CI results, some tests failed but should not be blocker 
issue

Thanks,
Cheng Pan


> On Mar 29, 2024, at 16:50, Jongyoul Lee  wrote:
> 
> Hell forks,
> 
> I missed the due date.
> 
> This vote will close at 2 AM on 2nd Apr PDT.
> 
> Best regards,
> Jongyoul Lee
> 
> 2024년 3월 29일 (금) 오후 5:47, Jongyoul Lee 님이 작성:
> 
>> Hello,
>> 
>> +1
>> 
>> Best regards,
>> Jongyoul Lee
>> 
>> 2024년 3월 29일 (금) 오후 5:30, Jongyoul Lee 님이 작성:
>> 
>>> Hi folks,
>>> 
>>> I propose the following RC to be released for the Apache Zeppelin
>>> 0.11.1 release.
>>> 
>>> 
>>> The commit id is 9a51785a3a86d93888a0d959815b097ba41b35d5 : 
>>> https://github.com/apache/zeppelin/commit/9a51785a3a86d93888a0d959815b097ba41b35d5
>>> 
>>> This corresponds to the tag: v0.11.1-rc1 : 
>>> https://github.com/apache/zeppelin/releases/tag/v0.11.1-rc1
>>> 
>>> The release archives (tgz), signature, and checksums are here 
>>> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.11.1-rc1/
>>> 
>>> The release candidate consists of the following source distribution archive
>>> zeppelin-0.11.1.tgz
>>> 
>>> In addition, the following supplementary binary distributions are provided
>>> for user convenience at the same location
>>> zeppelin-0.11.1-bin-all.tgz
>>> 
>>> 
>>> The maven artifacts are here
>>> 
>>> https://repository.apache.org/content/repositories/orgapachezeppelin-1336/org/apache/zeppelin/
>>> 
>>> You can find the KEYS file here: 
>>> https://dist.apache.org/repos/dist/release/zeppelin/KEYS
>>> 
>>> Release notes available at 
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316221=12354214
>>> 
>>> 
>>> For more information, this release has security fixes mostly.
>>> 
>>> Vote will be open for next 72 hours (close at 7am 8/Nov PDT).
>>> 
>>> [ ] +1 approve
>>> [ ] 0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>> 
>>> 
>> 
>> --
>> 이종열, Jongyoul Lee, 李宗烈
>> http://madeng.net
>> 
> 
> 
> -- 
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net

Re: [VOTE] Release Apache Zeppelin 0.11.1 (RC1)

[Jongyoul Lee]

Hell forks,

I missed the due date.

This vote will close at 2 AM on 2nd Apr PDT.

Best regards,
Jongyoul Lee

2024년 3월 29일 (금) 오후 5:47, Jongyoul Lee 님이 작성:

> Hello,
>
> +1
>
> Best regards,
> Jongyoul Lee
>
> 2024년 3월 29일 (금) 오후 5:30, Jongyoul Lee 님이 작성:
>
>> Hi folks,
>>
>> I propose the following RC to be released for the Apache Zeppelin
>> 0.11.1 release.
>>
>>
>> The commit id is 9a51785a3a86d93888a0d959815b097ba41b35d5 : 
>> https://github.com/apache/zeppelin/commit/9a51785a3a86d93888a0d959815b097ba41b35d5
>>
>> This corresponds to the tag: v0.11.1-rc1 : 
>> https://github.com/apache/zeppelin/releases/tag/v0.11.1-rc1
>>
>> The release archives (tgz), signature, and checksums are here 
>> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.11.1-rc1/
>>
>> The release candidate consists of the following source distribution archive
>> zeppelin-0.11.1.tgz
>>
>> In addition, the following supplementary binary distributions are provided
>> for user convenience at the same location
>> zeppelin-0.11.1-bin-all.tgz
>>
>>
>> The maven artifacts are here
>>
>> https://repository.apache.org/content/repositories/orgapachezeppelin-1336/org/apache/zeppelin/
>>
>> You can find the KEYS file here: 
>> https://dist.apache.org/repos/dist/release/zeppelin/KEYS
>>
>> Release notes available at 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316221=12354214
>>
>>
>> For more information, this release has security fixes mostly.
>>
>> Vote will be open for next 72 hours (close at 7am 8/Nov PDT).
>>
>> [ ] +1 approve
>> [ ] 0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>


-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

Re: [VOTE] Release Apache Zeppelin 0.11.1 (RC1)

[Jongyoul Lee]

Hello,

+1

Best regards,
Jongyoul Lee

2024년 3월 29일 (금) 오후 5:30, Jongyoul Lee 님이 작성:

> Hi folks,
>
> I propose the following RC to be released for the Apache Zeppelin
> 0.11.1 release.
>
>
> The commit id is 9a51785a3a86d93888a0d959815b097ba41b35d5 : 
> https://github.com/apache/zeppelin/commit/9a51785a3a86d93888a0d959815b097ba41b35d5
>
> This corresponds to the tag: v0.11.1-rc1 : 
> https://github.com/apache/zeppelin/releases/tag/v0.11.1-rc1
>
> The release archives (tgz), signature, and checksums are here 
> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.11.1-rc1/
>
> The release candidate consists of the following source distribution archive
> zeppelin-0.11.1.tgz
>
> In addition, the following supplementary binary distributions are provided
> for user convenience at the same location
> zeppelin-0.11.1-bin-all.tgz
>
>
> The maven artifacts are here
>
> https://repository.apache.org/content/repositories/orgapachezeppelin-1336/org/apache/zeppelin/
>
> You can find the KEYS file here: 
> https://dist.apache.org/repos/dist/release/zeppelin/KEYS
>
> Release notes available at 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316221=12354214
>
>
> For more information, this release has security fixes mostly.
>
> Vote will be open for next 72 hours (close at 7am 8/Nov PDT).
>
> [ ] +1 approve
> [ ] 0 no opinion
> [ ] -1 disapprove (and reason why)
>
>

-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

[VOTE] Release Apache Zeppelin 0.11.1 (RC1)

[Jongyoul Lee]

Hi folks,

I propose the following RC to be released for the Apache Zeppelin
0.11.1 release.


The commit id is 9a51785a3a86d93888a0d959815b097ba41b35d5 :
https://github.com/apache/zeppelin/commit/9a51785a3a86d93888a0d959815b097ba41b35d5

This corresponds to the tag: v0.11.1-rc1 :
https://github.com/apache/zeppelin/releases/tag/v0.11.1-rc1

The release archives (tgz), signature, and checksums are here
https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.11.1-rc1/

The release candidate consists of the following source distribution archive
zeppelin-0.11.1.tgz

In addition, the following supplementary binary distributions are provided
for user convenience at the same location
zeppelin-0.11.1-bin-all.tgz


The maven artifacts are here

https://repository.apache.org/content/repositories/orgapachezeppelin-1336/org/apache/zeppelin/

You can find the KEYS file here:
https://dist.apache.org/repos/dist/release/zeppelin/KEYS

Release notes available at
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316221=12354214


For more information, this release has security fixes mostly.

Vote will be open for next 72 hours (close at 7am 8/Nov PDT).

[ ] +1 approve
[ ] 0 no opinion
[ ] -1 disapprove (and reason why)

[jira] [Created] (ZEPPELIN-6006) Reducing command line applications

[Philipp Dallig (Jira)]

Philipp Dallig created ZEPPELIN-6006:


 Summary: Reducing command line applications
 Key: ZEPPELIN-6006
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6006
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Philipp Dallig
Assignee: Philipp Dallig


Some time ago, I had tried to build and test Zeppelin in a minimal OS 
container. I noticed dependencies to command line applications.
We should keep these to a minimum and let the JVM carry out the tasks.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Community Over Code NA 2024 Travel Assistance Applications now open!

[Gavin McDonald]

Hello to all users, contributors and Committers!

[ You are receiving this email as a subscriber to one or more ASF project
dev or user
  mailing lists and is not being sent to you directly. It is important that
we reach all of our
  users and contributors/committers so that they may get a chance to
benefit from this.
  We apologise in advance if this doesn't interest you but it is on topic
for the mailing
  lists of the Apache Software Foundation; and it is important please that
you do not
  mark this as spam in your email client. Thank You! ]

The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code NA 2024 are now
open!

We will be supporting Community over Code NA, Denver Colorado in
October 7th to the 10th 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this years applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Monday 6th May, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

For those that will need a Visa to enter the Country - we advise you apply
now so that you have enough time in case of interview delays. So do not
wait until you know if you have been accepted or not.

We look forward to greeting many of you in Denver, Colorado , October 2024!

Kind Regards,

Gavin

(On behalf of the Travel Assistance Committee)

[jira] [Created] (ZEPPELIN-6005) Update Kyuubi JDBC docs

[Cheng Pan (Jira)]

Cheng Pan created ZEPPELIN-6005:
---

 Summary: Update Kyuubi JDBC docs
 Key: ZEPPELIN-6005
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6005
 Project: Zeppelin
  Issue Type: Improvement
  Components: JdbcInterpreter
Reporter: Cheng Pan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-6004) ConcurrentModificationException in zeppelin-client UpdateStreamSqlJob buildResult

[zhengyuan (Jira)]

zhengyuan created ZEPPELIN-6004:
---

 Summary: ConcurrentModificationException in zeppelin-client 
UpdateStreamSqlJob buildResult
 Key: ZEPPELIN-6004
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6004
 Project: Zeppelin
  Issue Type: Bug
  Components: zeppelin-client
Affects Versions: 0.11.0
Reporter: zhengyuan


{code:java}
//代码占位符
String paragraphId = zClient.addParagraph(noteId, "the first paragraph", 
this.getTestSql());
 zClient.submitNote(noteId);
 NoteResult noteResult = zClient.waitUntilNoteFinished(noteId);
 System.out.println("Submit note and the note result: " + noteResult); {code}
detail logs:



Submit note and the note result: NoteResult{noteId='2JTW2E269', 
isRunning=false, 
paragraphResultList=[ParagraphResult{paragraphId='paragraph_1710750700587_868085398',
 status=ERROR, results=Result{type='TEXT', data='Fail to run sql command: 
select * from v_meta_attr_processing_3
java.lang.RuntimeException: Fail to run update type stream job
    at 
org.apache.zeppelin.flink.FlinkStreamSqlInterpreter.callInnerSelect(FlinkStreamSqlInterpreter.java:93)
    at 
org.apache.zeppelin.flink.FlinkStreamSqlInterpreter.lambda$open$0(FlinkStreamSqlInterpreter.java:48)
    at 
org.apache.zeppelin.flink.Flink116SqlInterpreter.callStreamInnerSelect(Flink116SqlInterpreter.java:446)
    at 
org.apache.zeppelin.flink.Flink116SqlInterpreter.callSelect(Flink116SqlInterpreter.java:430)
    at 
org.apache.zeppelin.flink.Flink116SqlInterpreter.callOperation(Flink116SqlInterpreter.java:290)
    at 
org.apache.zeppelin.flink.Flink116SqlInterpreter.runSqlList(Flink116SqlInterpreter.java:236)
    at 
org.apache.zeppelin.flink.Flink116Shims.runSqlList(Flink116Shims.java:394)
    at 
org.apache.zeppelin.flink.FlinkStreamSqlInterpreter.runSqlList(FlinkStreamSqlInterpreter.java:102)
    at 
org.apache.zeppelin.flink.FlinkSqlInterpreter.internalInterpret(FlinkSqlInterpreter.java:58)
    at 
org.apache.zeppelin.interpreter.AbstractInterpreter.interpret(AbstractInterpreter.java:55)
    at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:108)
    at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:877)
    at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:769)
    at org.apache.zeppelin.scheduler.Job.run(Job.java:186)
    at 
org.apache.zeppelin.scheduler.AbstractScheduler.runJob(AbstractScheduler.java:135)
    at 
org.apache.zeppelin.scheduler.ParallelScheduler.lambda$runJobInScheduler$0(ParallelScheduler.java:46)
    at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Fail to run stream sql job
    at 
org.apache.zeppelin.flink.sql.AbstractStreamSqlJob.run(AbstractStreamSqlJob.java:165)
    at 
org.apache.zeppelin.flink.sql.AbstractStreamSqlJob.run(AbstractStreamSqlJob.java:109)
    at 
org.apache.zeppelin.flink.FlinkStreamSqlInterpreter.callInnerSelect(FlinkStreamSqlInterpreter.java:91)
    ... 18 more
Caused by: java.util.ConcurrentModificationException
    at java.util.ArrayList.sort(ArrayList.java:1466)
    at 
org.apache.zeppelin.flink.sql.UpdateStreamSqlJob.buildResult(UpdateStreamSqlJob.java:91)
    at 
org.apache.zeppelin.flink.sql.UpdateStreamSqlJob.refresh(UpdateStreamSqlJob.java:105)
    at 
org.apache.zeppelin.flink.sql.AbstractStreamSqlJob.run(AbstractStreamSqlJob.java:159)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-6003) Log detail info of SQL in JDBCInterpreter

[Manhua Jiang (Jira)]

Manhua Jiang created ZEPPELIN-6003:
--

 Summary: Log detail info of SQL in JDBCInterpreter
 Key: ZEPPELIN-6003
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6003
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Manhua Jiang


Currently we can monitor running SQL in JDBCInterpreter  but unable to know 
who/which note fire the SQL, especially a couple of users using zeppelin at the 
same time. 
 
Bond the SQL with additional info,  we can inform the user with 
user/noteid/paragragh info  if needed



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-6002) Fix completer NPE

[Manhua Jiang (Jira)]

Manhua Jiang created ZEPPELIN-6002:
--

 Summary: Fix completer NPE
 Key: ZEPPELIN-6002
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6002
 Project: Zeppelin
  Issue Type: Bug
Reporter: Manhua Jiang


NPE occur when adding the driver specific SQL completions. Some 
driver(hive-jdbc-uber-2.6.5.0-292.jar in my case) does not implement method 
{{DatabaseMetaData.getDriverName()}} well and cause exception , then fail to 
initialize {{{}keywordCompleter{}}}.

Since it is optional, we should avoid such driver interfere the default one, 
and log it for the profession



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-6001) Update Dockerfile after Release

[Philipp Dallig (Jira)]

Philipp Dallig created ZEPPELIN-6001:


 Summary: Update Dockerfile after Release
 Key: ZEPPELIN-6001
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6001
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Philipp Dallig






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-6000) Polish zengine tests

[Philipp Dallig (Jira)]

Philipp Dallig created ZEPPELIN-6000:


 Summary: Polish zengine tests
 Key: ZEPPELIN-6000
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6000
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Philipp Dallig
Assignee: Philipp Dallig






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5999) Remove instance Objects out of Zeppelin

[Philipp Dallig (Jira)]

Philipp Dallig created ZEPPELIN-5999:


 Summary: Remove instance Objects out of Zeppelin
 Key: ZEPPELIN-5999
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5999
 Project: Zeppelin
  Issue Type: Task
Reporter: Philipp Dallig
Assignee: Philipp Dallig


Currently Zeppelin has some static instance objects (PluginManager, 
ZeppelinConfiguration, ConfigStorage) which can lead to strange behavior when 
we change the objects during tests.

Zeppelin has some workarounds:
 - ZeppelinConfiguration.reset();
 - PluginManager.reset();

But these workarounds are not thread-safe and we cannot start multiple 
ZeppelinServers at once.

We should also not use `System.setProperty(..., ...)` to change the 
configuration during the test runtime. This has an effect on other tests



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5998) Verify executables

[Jongyoul Lee (Jira)]

Jongyoul Lee created ZEPPELIN-5998:
--

 Summary: Verify executables
 Key: ZEPPELIN-5998
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5998
 Project: Zeppelin
  Issue Type: Task
Reporter: Jongyoul Lee


Zeppelin uses pre-installed executables when running it. It would be good to 
check if executables are not infected.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5997) Upgrade to Java 11 as the minimum version

[PJ Fanning (Jira)]

PJ Fanning created ZEPPELIN-5997:


 Summary: Upgrade to Java 11 as the minimum version
 Key: ZEPPELIN-5997
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5997
 Project: Zeppelin
  Issue Type: Task
Reporter: PJ Fanning


Zeppelin is an application so you have more leeway to upgrade than lib 
maintainers do.

Some of the dependencies that Zeppelin uses have already abandoned Java 8 
support.

There is even an argument to go for Java 17. Spring has already abandoned Java 
11.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5996) Zeppelin bundles json-20180813.jar but this has a Category X license

[PJ Fanning (Jira)]

PJ Fanning created ZEPPELIN-5996:


 Summary: Zeppelin bundles json-20180813.jar but this has a 
Category X license
 Key: ZEPPELIN-5996
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5996
 Project: Zeppelin
  Issue Type: Task
Reporter: PJ Fanning


https://www.apache.org/legal/resolved.html lists this as nonsensical and not 
allowed in ASF projects.

JSON License - links to https://www.json.org/license.html

Prevents the jar being used for evil.

In theory, we can force an upgrade to a version that uses Public Domain and 
gets rid of the good vs evil nonsense.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Community Over Code Asia 2024 Travel Assistance Applications now open!

[Gavin McDonald]

Hello to all users, contributors and Committers!

The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code Asia 2024 are now
open!

We will be supporting Community over Code Asia, Hangzhou, China
July 26th - 28th, 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this year's applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Friday, May 10th, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

For those that will need a Visa to enter the Country - we advise you to
apply
now so that you have enough time in case of interview delays. So do not
wait until you know if you have been accepted or not.

We look forward to greeting many of you in Hangzhou, China in July, 2024!

Kind Regards,

Gavin

(On behalf of the Travel Assistance Committee)

Re: [ANNOUCE] Zeppelin 0.11.0 is released

[Jongyoul Lee]

Hello,

Thank you for checking it. I released them by the way.

Best regards,
Jongyoul Lee

2024년 2월 17일 (토) 오전 3:22, PJ Fanning 님이 작성:

> I did a quick verification of some 0.11.0 jars and they seem fine.
>
> Regarding the sap jar - that has a reported security issue, so we will
> need to say in the CVE that it will never be fixed.
>
> On 2024/02/16 16:32:20 Jongyoul Lee wrote:
> > Hello PJ Fanning,
> >
> > Thank you for checking it. BTW, zeppelin:sap is deprecated and it won't
> be
> > released in 0.11.0. Is there any concern that I have to take care of it?
> >
> > Best regards,
> > Jongyoul
> >
> > 2024년 2월 16일 (금) 오후 11:43, PJ Fanning 님이 작성:
> >
> > > My verification is incomplete but I did find that at least one jar is
> > > missing from:
> > >
> https://repository.apache.org/content/groups/staging/org/apache/zeppelin/
> > >
> > > The `org.apache.zeppelin:sap` jar is missing for v0.11.0.
> > >
> > >
> > >
> > > On 2024/02/16 13:29:29 PJ Fanning wrote:
> > > > Thanks Jongyoul. I can see the jars in repository.apache.org and I
> can
> > > see the release button.
> > > >
> > > > Could you leave the jars for a day or so that people can have a look
> at
> > > them? I can have a quick look tonight.
> > > >
> > > > On 2024/02/16 12:48:12 Jongyoul Lee wrote:
> > > > > Hello,
> > > > >
> > > > > Sorry, I missed it. I uploaded them now but I cannot find the
> release
> > > > > button. Should I get another permission to release it?
> > > > >
> > > > > Could you please check it?
> > > > >
> > > > > Best regards,
> > > > > Jongyoul
> > > > >
> > > > > 2024년 2월 16일 (금) 오전 9:45, PJ Fanning 님이 작성:
> > > > >
> > > > > > Congratulations to everyone on the release.
> > > > > >
> > > > > > I was looking at Maven Central and the Apache Nexus Server [1]
> and
> > > the
> > > > > > 0.11.0 jars do not appear to have been released. Is there a plan
> to
> > > release
> > > > > > them?
> > > > > >
> > > > > > [1] https://repository.apache.org/
> > > > > >
> > > > > > On 2024/02/11 17:24:29 Jongyoul Lee wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > The Apache Zeppelin community is pleased to announce the
> > > availability
> > > > > > > of the 0.11.0 release.
> > > > > > >
> > > > > > > Zeppelin is a collaborative data analytics and visualization
> tool
> > > for
> > > > > > > distributed, general-purpose data processing system such as
> Apache
> > > > > > > Spark, Apache Flink, Apache Cassandra and etc.
> > > > > > >
> > > > > > > It is the first release in two years. The community improved to
> > > Java
> > > > > > > 11, Spark 3.5, Flink 1.17, and Python 3.9.
> > > > > > >
> > > > > > > We encourage you to download the latest release
> > > > > > > fromhttp://zeppelin.apache.org/download.html
> > > > > > >
> > > > > > > The easiest way to try Zeppelin is to run the shipped tutorial
> > > notes
> > > > > > > via docker image
> > > > > > >
> > > > > > >
> > > > > >
> > >
> https://zeppelin.apache.org/download.html#using-the-official-docker-image
> > > > > > >
> > > > > > > We welcome your help and feedback. For more information on the
> > > project
> > > > > > > and how to get involved, visit our website at
> > > > > > > http://zeppelin.apache.org/
> > > > > > >
> > > > > > > Thank you all users and contributors who have helped to improve
> > > Apache
> > > > > > > Zeppelin. Welcome to join our community to discuss with others
> > > > > > >
> > > https://zeppelin.apache.org/community.html#mailing-list--slack-channel
> > > > > > >
> > > > > > >
> > > > > > > Best regards,
> > > > > > >
> > > > > > > Jongyoul Lee
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > 이종열, Jongyoul Lee, 李宗烈
> > > > > http://madeng.net
> > > > >
> > > >
> > >
> >
> >
> > --
> > 이종열, Jongyoul Lee, 李宗烈
> > http://madeng.net
> >
>


-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

Re: [ANNOUCE] Zeppelin 0.11.0 is released

[PJ Fanning]

I did a quick verification of some 0.11.0 jars and they seem fine.

Regarding the sap jar - that has a reported security issue, so we will need to 
say in the CVE that it will never be fixed.

On 2024/02/16 16:32:20 Jongyoul Lee wrote:
> Hello PJ Fanning,
> 
> Thank you for checking it. BTW, zeppelin:sap is deprecated and it won't be
> released in 0.11.0. Is there any concern that I have to take care of it?
> 
> Best regards,
> Jongyoul
> 
> 2024년 2월 16일 (금) 오후 11:43, PJ Fanning 님이 작성:
> 
> > My verification is incomplete but I did find that at least one jar is
> > missing from:
> > https://repository.apache.org/content/groups/staging/org/apache/zeppelin/
> >
> > The `org.apache.zeppelin:sap` jar is missing for v0.11.0.
> >
> >
> >
> > On 2024/02/16 13:29:29 PJ Fanning wrote:
> > > Thanks Jongyoul. I can see the jars in repository.apache.org and I can
> > see the release button.
> > >
> > > Could you leave the jars for a day or so that people can have a look at
> > them? I can have a quick look tonight.
> > >
> > > On 2024/02/16 12:48:12 Jongyoul Lee wrote:
> > > > Hello,
> > > >
> > > > Sorry, I missed it. I uploaded them now but I cannot find the release
> > > > button. Should I get another permission to release it?
> > > >
> > > > Could you please check it?
> > > >
> > > > Best regards,
> > > > Jongyoul
> > > >
> > > > 2024년 2월 16일 (금) 오전 9:45, PJ Fanning 님이 작성:
> > > >
> > > > > Congratulations to everyone on the release.
> > > > >
> > > > > I was looking at Maven Central and the Apache Nexus Server [1] and
> > the
> > > > > 0.11.0 jars do not appear to have been released. Is there a plan to
> > release
> > > > > them?
> > > > >
> > > > > [1] https://repository.apache.org/
> > > > >
> > > > > On 2024/02/11 17:24:29 Jongyoul Lee wrote:
> > > > > > Hello,
> > > > > >
> > > > > > The Apache Zeppelin community is pleased to announce the
> > availability
> > > > > > of the 0.11.0 release.
> > > > > >
> > > > > > Zeppelin is a collaborative data analytics and visualization tool
> > for
> > > > > > distributed, general-purpose data processing system such as Apache
> > > > > > Spark, Apache Flink, Apache Cassandra and etc.
> > > > > >
> > > > > > It is the first release in two years. The community improved to
> > Java
> > > > > > 11, Spark 3.5, Flink 1.17, and Python 3.9.
> > > > > >
> > > > > > We encourage you to download the latest release
> > > > > > fromhttp://zeppelin.apache.org/download.html
> > > > > >
> > > > > > The easiest way to try Zeppelin is to run the shipped tutorial
> > notes
> > > > > > via docker image
> > > > > >
> > > > > >
> > > > >
> > https://zeppelin.apache.org/download.html#using-the-official-docker-image
> > > > > >
> > > > > > We welcome your help and feedback. For more information on the
> > project
> > > > > > and how to get involved, visit our website at
> > > > > > http://zeppelin.apache.org/
> > > > > >
> > > > > > Thank you all users and contributors who have helped to improve
> > Apache
> > > > > > Zeppelin. Welcome to join our community to discuss with others
> > > > > >
> > https://zeppelin.apache.org/community.html#mailing-list--slack-channel
> > > > > >
> > > > > >
> > > > > > Best regards,
> > > > > >
> > > > > > Jongyoul Lee
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > 이종열, Jongyoul Lee, 李宗烈
> > > > http://madeng.net
> > > >
> > >
> >
> 
> 
> -- 
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
> 

Re: [ANNOUCE] Zeppelin 0.11.0 is released

[Jongyoul Lee]

Hello PJ Fanning,

Thank you for checking it. BTW, zeppelin:sap is deprecated and it won't be
released in 0.11.0. Is there any concern that I have to take care of it?

Best regards,
Jongyoul

2024년 2월 16일 (금) 오후 11:43, PJ Fanning 님이 작성:

> My verification is incomplete but I did find that at least one jar is
> missing from:
> https://repository.apache.org/content/groups/staging/org/apache/zeppelin/
>
> The `org.apache.zeppelin:sap` jar is missing for v0.11.0.
>
>
>
> On 2024/02/16 13:29:29 PJ Fanning wrote:
> > Thanks Jongyoul. I can see the jars in repository.apache.org and I can
> see the release button.
> >
> > Could you leave the jars for a day or so that people can have a look at
> them? I can have a quick look tonight.
> >
> > On 2024/02/16 12:48:12 Jongyoul Lee wrote:
> > > Hello,
> > >
> > > Sorry, I missed it. I uploaded them now but I cannot find the release
> > > button. Should I get another permission to release it?
> > >
> > > Could you please check it?
> > >
> > > Best regards,
> > > Jongyoul
> > >
> > > 2024년 2월 16일 (금) 오전 9:45, PJ Fanning 님이 작성:
> > >
> > > > Congratulations to everyone on the release.
> > > >
> > > > I was looking at Maven Central and the Apache Nexus Server [1] and
> the
> > > > 0.11.0 jars do not appear to have been released. Is there a plan to
> release
> > > > them?
> > > >
> > > > [1] https://repository.apache.org/
> > > >
> > > > On 2024/02/11 17:24:29 Jongyoul Lee wrote:
> > > > > Hello,
> > > > >
> > > > > The Apache Zeppelin community is pleased to announce the
> availability
> > > > > of the 0.11.0 release.
> > > > >
> > > > > Zeppelin is a collaborative data analytics and visualization tool
> for
> > > > > distributed, general-purpose data processing system such as Apache
> > > > > Spark, Apache Flink, Apache Cassandra and etc.
> > > > >
> > > > > It is the first release in two years. The community improved to
> Java
> > > > > 11, Spark 3.5, Flink 1.17, and Python 3.9.
> > > > >
> > > > > We encourage you to download the latest release
> > > > > fromhttp://zeppelin.apache.org/download.html
> > > > >
> > > > > The easiest way to try Zeppelin is to run the shipped tutorial
> notes
> > > > > via docker image
> > > > >
> > > > >
> > > >
> https://zeppelin.apache.org/download.html#using-the-official-docker-image
> > > > >
> > > > > We welcome your help and feedback. For more information on the
> project
> > > > > and how to get involved, visit our website at
> > > > > http://zeppelin.apache.org/
> > > > >
> > > > > Thank you all users and contributors who have helped to improve
> Apache
> > > > > Zeppelin. Welcome to join our community to discuss with others
> > > > >
> https://zeppelin.apache.org/community.html#mailing-list--slack-channel
> > > > >
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Jongyoul Lee
> > > > >
> > > >
> > >
> > >
> > > --
> > > 이종열, Jongyoul Lee, 李宗烈
> > > http://madeng.net
> > >
> >
>


-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

Re: [ANNOUCE] Zeppelin 0.11.0 is released

[PJ Fanning]

My verification is incomplete but I did find that at least one jar is missing 
from:
https://repository.apache.org/content/groups/staging/org/apache/zeppelin/

The `org.apache.zeppelin:sap` jar is missing for v0.11.0.



On 2024/02/16 13:29:29 PJ Fanning wrote:
> Thanks Jongyoul. I can see the jars in repository.apache.org and I can see 
> the release button.
> 
> Could you leave the jars for a day or so that people can have a look at them? 
> I can have a quick look tonight.
> 
> On 2024/02/16 12:48:12 Jongyoul Lee wrote:
> > Hello,
> > 
> > Sorry, I missed it. I uploaded them now but I cannot find the release
> > button. Should I get another permission to release it?
> > 
> > Could you please check it?
> > 
> > Best regards,
> > Jongyoul
> > 
> > 2024년 2월 16일 (금) 오전 9:45, PJ Fanning 님이 작성:
> > 
> > > Congratulations to everyone on the release.
> > >
> > > I was looking at Maven Central and the Apache Nexus Server [1] and the
> > > 0.11.0 jars do not appear to have been released. Is there a plan to 
> > > release
> > > them?
> > >
> > > [1] https://repository.apache.org/
> > >
> > > On 2024/02/11 17:24:29 Jongyoul Lee wrote:
> > > > Hello,
> > > >
> > > > The Apache Zeppelin community is pleased to announce the availability
> > > > of the 0.11.0 release.
> > > >
> > > > Zeppelin is a collaborative data analytics and visualization tool for
> > > > distributed, general-purpose data processing system such as Apache
> > > > Spark, Apache Flink, Apache Cassandra and etc.
> > > >
> > > > It is the first release in two years. The community improved to Java
> > > > 11, Spark 3.5, Flink 1.17, and Python 3.9.
> > > >
> > > > We encourage you to download the latest release
> > > > fromhttp://zeppelin.apache.org/download.html
> > > >
> > > > The easiest way to try Zeppelin is to run the shipped tutorial notes
> > > > via docker image
> > > >
> > > >
> > > https://zeppelin.apache.org/download.html#using-the-official-docker-image
> > > >
> > > > We welcome your help and feedback. For more information on the project
> > > > and how to get involved, visit our website at
> > > > http://zeppelin.apache.org/
> > > >
> > > > Thank you all users and contributors who have helped to improve Apache
> > > > Zeppelin. Welcome to join our community to discuss with others
> > > > https://zeppelin.apache.org/community.html#mailing-list--slack-channel
> > > >
> > > >
> > > > Best regards,
> > > >
> > > > Jongyoul Lee
> > > >
> > >
> > 
> > 
> > -- 
> > 이종열, Jongyoul Lee, 李宗烈
> > http://madeng.net
> > 
> 

Re: [ANNOUCE] Zeppelin 0.11.0 is released

[PJ Fanning]

Thanks Jongyoul. I can see the jars in repository.apache.org and I can see the 
release button.

Could you leave the jars for a day or so that people can have a look at them? I 
can have a quick look tonight.

On 2024/02/16 12:48:12 Jongyoul Lee wrote:
> Hello,
> 
> Sorry, I missed it. I uploaded them now but I cannot find the release
> button. Should I get another permission to release it?
> 
> Could you please check it?
> 
> Best regards,
> Jongyoul
> 
> 2024년 2월 16일 (금) 오전 9:45, PJ Fanning 님이 작성:
> 
> > Congratulations to everyone on the release.
> >
> > I was looking at Maven Central and the Apache Nexus Server [1] and the
> > 0.11.0 jars do not appear to have been released. Is there a plan to release
> > them?
> >
> > [1] https://repository.apache.org/
> >
> > On 2024/02/11 17:24:29 Jongyoul Lee wrote:
> > > Hello,
> > >
> > > The Apache Zeppelin community is pleased to announce the availability
> > > of the 0.11.0 release.
> > >
> > > Zeppelin is a collaborative data analytics and visualization tool for
> > > distributed, general-purpose data processing system such as Apache
> > > Spark, Apache Flink, Apache Cassandra and etc.
> > >
> > > It is the first release in two years. The community improved to Java
> > > 11, Spark 3.5, Flink 1.17, and Python 3.9.
> > >
> > > We encourage you to download the latest release
> > > fromhttp://zeppelin.apache.org/download.html
> > >
> > > The easiest way to try Zeppelin is to run the shipped tutorial notes
> > > via docker image
> > >
> > >
> > https://zeppelin.apache.org/download.html#using-the-official-docker-image
> > >
> > > We welcome your help and feedback. For more information on the project
> > > and how to get involved, visit our website at
> > > http://zeppelin.apache.org/
> > >
> > > Thank you all users and contributors who have helped to improve Apache
> > > Zeppelin. Welcome to join our community to discuss with others
> > > https://zeppelin.apache.org/community.html#mailing-list--slack-channel
> > >
> > >
> > > Best regards,
> > >
> > > Jongyoul Lee
> > >
> >
> 
> 
> -- 
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
> 

Re: [ANNOUCE] Zeppelin 0.11.0 is released

[Jongyoul Lee]

Hello,

Sorry, I missed it. I uploaded them now but I cannot find the release
button. Should I get another permission to release it?

Could you please check it?

Best regards,
Jongyoul

2024년 2월 16일 (금) 오전 9:45, PJ Fanning 님이 작성:

> Congratulations to everyone on the release.
>
> I was looking at Maven Central and the Apache Nexus Server [1] and the
> 0.11.0 jars do not appear to have been released. Is there a plan to release
> them?
>
> [1] https://repository.apache.org/
>
> On 2024/02/11 17:24:29 Jongyoul Lee wrote:
> > Hello,
> >
> > The Apache Zeppelin community is pleased to announce the availability
> > of the 0.11.0 release.
> >
> > Zeppelin is a collaborative data analytics and visualization tool for
> > distributed, general-purpose data processing system such as Apache
> > Spark, Apache Flink, Apache Cassandra and etc.
> >
> > It is the first release in two years. The community improved to Java
> > 11, Spark 3.5, Flink 1.17, and Python 3.9.
> >
> > We encourage you to download the latest release
> > fromhttp://zeppelin.apache.org/download.html
> >
> > The easiest way to try Zeppelin is to run the shipped tutorial notes
> > via docker image
> >
> >
> https://zeppelin.apache.org/download.html#using-the-official-docker-image
> >
> > We welcome your help and feedback. For more information on the project
> > and how to get involved, visit our website at
> > http://zeppelin.apache.org/
> >
> > Thank you all users and contributors who have helped to improve Apache
> > Zeppelin. Welcome to join our community to discuss with others
> > https://zeppelin.apache.org/community.html#mailing-list--slack-channel
> >
> >
> > Best regards,
> >
> > Jongyoul Lee
> >
>


-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

Re: [ANNOUCE] Zeppelin 0.11.0 is released

[PJ Fanning]

Congratulations to everyone on the release.

I was looking at Maven Central and the Apache Nexus Server [1] and the 0.11.0 
jars do not appear to have been released. Is there a plan to release them?

[1] https://repository.apache.org/

On 2024/02/11 17:24:29 Jongyoul Lee wrote:
> Hello,
> 
> The Apache Zeppelin community is pleased to announce the availability
> of the 0.11.0 release.
> 
> Zeppelin is a collaborative data analytics and visualization tool for
> distributed, general-purpose data processing system such as Apache
> Spark, Apache Flink, Apache Cassandra and etc.
> 
> It is the first release in two years. The community improved to Java
> 11, Spark 3.5, Flink 1.17, and Python 3.9.
> 
> We encourage you to download the latest release
> fromhttp://zeppelin.apache.org/download.html
> 
> The easiest way to try Zeppelin is to run the shipped tutorial notes
> via docker image
> 
> https://zeppelin.apache.org/download.html#using-the-official-docker-image
> 
> We welcome your help and feedback. For more information on the project
> and how to get involved, visit our website at
> http://zeppelin.apache.org/
> 
> Thank you all users and contributors who have helped to improve Apache
> Zeppelin. Welcome to join our community to discuss with others
> https://zeppelin.apache.org/community.html#mailing-list--slack-channel
> 
> 
> Best regards,
> 
> Jongyoul Lee
> 

[jira] [Created] (ZEPPELIN-5995) Update K8s-Library

[Philipp Dallig (Jira)]

Philipp Dallig created ZEPPELIN-5995:


 Summary: Update K8s-Library
 Key: ZEPPELIN-5995
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5995
 Project: Zeppelin
  Issue Type: Task
Reporter: Philipp Dallig
Assignee: Philipp Dallig


I am hoping for a more stable test environment with the update



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5994) Fix cron tests for ZeppelinRestApiTest

[Jongyoul Lee (Jira)]

Jongyoul Lee created ZEPPELIN-5994:
--

 Summary: Fix cron tests for ZeppelinRestApiTest
 Key: ZEPPELIN-5994
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5994
 Project: Zeppelin
  Issue Type: Task
Affects Versions: 0.11.1
Reporter: Jongyoul Lee


For security, the cron feature will be disabled in anonymous mode. it tests in 
ZeppelinRestApiTest without authentication mode. I disabled them first and will 
fix them



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5993) Enable GCS Notebookrepo Tests

[Philipp Dallig (Jira)]

Philipp Dallig created ZEPPELIN-5993:


 Summary: Enable GCS Notebookrepo Tests
 Key: ZEPPELIN-5993
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5993
 Project: Zeppelin
  Issue Type: Bug
Reporter: Philipp Dallig
Assignee: Philipp Dallig


We should enable the JUnit tests for gcs



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[ANNOUCE] Zeppelin 0.11.0 is released

[Jongyoul Lee]

Hello,

The Apache Zeppelin community is pleased to announce the availability
of the 0.11.0 release.

Zeppelin is a collaborative data analytics and visualization tool for
distributed, general-purpose data processing system such as Apache
Spark, Apache Flink, Apache Cassandra and etc.

It is the first release in two years. The community improved to Java
11, Spark 3.5, Flink 1.17, and Python 3.9.

We encourage you to download the latest release
fromhttp://zeppelin.apache.org/download.html

The easiest way to try Zeppelin is to run the shipped tutorial notes
via docker image

https://zeppelin.apache.org/download.html#using-the-official-docker-image

We welcome your help and feedback. For more information on the project
and how to get involved, visit our website at
http://zeppelin.apache.org/

Thank you all users and contributors who have helped to improve Apache
Zeppelin. Welcome to join our community to discuss with others
https://zeppelin.apache.org/community.html#mailing-list--slack-channel


Best regards,

Jongyoul Lee

[RESULT] [VOTE] Release Apache Zeppelin 0.11.0 (RC1)

[Jongyoul Lee]

Hello,

The vote passes with 4 binding +1 votes, 1 non-binding +1 votes, and not +0
or -1 votes. Thanks to everyone who verified rc and voted.

+1:
Michael Matsko
Jeff Zhang*
Philipp Dallig*
Guanhua Li*
Jongyoul Lee*

+0:

-1:

*binding

Vote thread:
https://lists.apache.org/thread/dg4nn1dgoh52ss8owvm61jbdt3bo16zx

Best regards,
Jongyoul Lee

[jira] [Created] (ZEPPELIN-5992) Can't work with data after cron execution

[Yaroslav Dolin (Jira)]

Yaroslav Dolin created ZEPPELIN-5992:


 Summary: Can't work with data after cron execution
 Key: ZEPPELIN-5992
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5992
 Project: Zeppelin
  Issue Type: Task
  Components: docker, Interpreters, python-interpreter
Affects Versions: 0.10.1
Reporter: Yaroslav Dolin
 Attachments: Screenshot 2024-02-08 at 11.47.54.png, log.txt

I can't work with data after cron execution with python interpreter

!Screenshot 2024-02-08 at 11.47.54.png!

I didn't find information in documentation. Also i don't have an option "After 
execution stop the interpreter". It's only in new interface, and cron configure 
doesn't work from new interface.

I attached logs.

How i can fix it? 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5991) Add support for DocumentDb and Mongo Atlas for Mongo Interpreter

[Mithun Mandal (Jira)]

Mithun Mandal created ZEPPELIN-5991:
---

 Summary: Add support for DocumentDb and Mongo Atlas for Mongo 
Interpreter
 Key: ZEPPELIN-5991
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5991
 Project: Zeppelin
  Issue Type: Improvement
  Components: interpreter-setting
Affects Versions: 0.10.2
Reporter: Mithun Mandal
 Fix For: 0.10.2


Currently Mongo interpreter has basic connection params which does not include 
any SSL / TSL. also mongo protocol is fixed.

 

DocumentDB: it required SSL / TSL connection.

Mongo Atlas: required different protocol mongodb+srv

Configuration:

mongo.server.protocol  for protocol specification

mongo.server.api.version for API version specification

 

SSL / TSL config

mongo.server.ssl.enabled  

mongo.server.tls.enabled

mongo.server.ca.file

mongo.server.allowInvalid

 

AWS specific additional configuration

mongo.server.aws.fle.awsAccessKeyId

mongo.server.aws.fle.awsSecretAccessKey

mongo.server.aws.fle.awsSessionToken

mongo.server.aws.fle.keyVaultNamespace



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5990) Disable sesitive configuration for JDBC url

[Jongyoul Lee (Jira)]

Jongyoul Lee created ZEPPELIN-5990:
--

 Summary: Disable sesitive configuration for JDBC url
 Key: ZEPPELIN-5990
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5990
 Project: Zeppelin
  Issue Type: Task
Affects Versions: 0.10.1, 0.11.0
Reporter: Jongyoul Lee
Assignee: Jongyoul Lee
 Fix For: 0.11.1, 0.12.0


Some JDBC configurations may make potential security issues so I want to 
disable the configurations.

 

ref. 
https://github.com/apache/dolphinscheduler/blob/dev/dolphinscheduler-datasource-plugin/dolphinscheduler-datasource-mysql/src/main/java/org/apache/dolphinscheduler/plugin/datasource/mysql/param/MySQLDataSourceProcessor.java



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[VOTE] Release Apache Zeppelin 0.11.0 RC1

[Jongyoul Lee]

Hi folks,

I propose the following RC to be released for the Apache Zeppelin 0.11.0
release.

The commit id is 523075a498ea6b72109fd817bab95f5d7fcb2829:
https://github.com/apache/zeppelin/commit/523075a498ea6b72109fd817bab95f5d7fcb2829

This corresponds to the tag: v0.11.0-rc1:
https://github.com/apache/zeppelin/tree/v0.11.0-rc1

The release archives, signature, and checksums are here:
https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.11.0-rc1/

The release candidate consists of the following source distributions
in zeppelin-0.11.0.tgz

In addition, the following supplementary binary distributions are provided
for user convenience at the same location as zeppelin-0.11.0-bin-all-tgz

You can find the KEYS file here:
https://dist.apache.org/repos/dist/release/zeppelin/KEYS

Release notes are available at
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316221=12350539

Shortly, this release resolves 257 issues including fixing security issues
from the last release.

Vote will be open for next 72 hours. (close at 4AM 8th Feb PDT)

[] +1 approve
[] 0 no opinion
[] -1 disapprove (and reason why)

Best regards,
Jongyoul Lee

Community over Code EU 2024 Travel Assistance Applications now open!

[Gavin McDonald]

Hello to all users, contributors and Committers!

The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code EU 2024 are now
open!

We will be supporting Community over Code EU, Bratislava, Slovakia,
June 3th - 5th, 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this years applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Friday, March 1st, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

For those that will need a Visa to enter the Country - we advise you apply
now so that you have enough time in case of interview delays. So do not
wait until you know if you have been accepted or not.

We look forward to greeting many of you in Bratislava, Slovakia in June,
2024!

Kind Regards,

Gavin

(On behalf of the Travel Assistance Committee)

Help requested: Zeppelin Security triage and follow-up

[Apache Security Team]

Dear Zeppelin community,

As you know, the Apache Software Foundation really cares about our users'
security, and protects them by defining sensible release and security
processes. These indirectly also protect our committers, shielding
individuals from personal liability. Additionally, we have a security
committee to assist PMCs with the process of triage and followup. Some of
this process is necessarily done in private; as we practice responsible
disclosure.

We see potential security issues are being reported privately to the
Zeppelin PMC, but the PMC is struggling to triage (and, if necessary, fix
and disclose) them in a timely manner. If we cannot turn this trend around
soon, Zeppelin will have to start the Apache Attic process.

On behalf of the PMC: would anyone be interested in significantly helping
out here? If so, please contact priv...@zeppelin.apache.org with
secur...@apache.org in Cc.


Kind regards,

The ASF Security Team

[jira] [Created] (ZEPPELIN-5989) Default notebook path resolving failed on windows

[Guorong Xu (Jira)]

Guorong Xu created ZEPPELIN-5989:


 Summary: Default notebook path resolving failed on windows
 Key: ZEPPELIN-5989
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5989
 Project: Zeppelin
  Issue Type: Bug
  Components: zeppelin-server
 Environment: sys: windows 10

IDE: IDEA

branch: master

 
Reporter: Guorong Xu


I'm trying to start the zeppelin without configuration file in my IDE on 
windows, and i get error as below:


```bash
java.io.IOException: java.net.URISyntaxException: Illegal character in path at 
index 2: ./\notebook
    at 
org.apache.zeppelin.notebook.repo.VFSNotebookRepo.setNotebookDirectory(VFSNotebookRepo.java:76)
    at 
org.apache.zeppelin.notebook.repo.GitNotebookRepo.init(GitNotebookRepo.java:74)
    at 
org.apache.zeppelin.notebook.repo.NotebookRepoSync.init(NotebookRepoSync.java:83)
    at 
org.apache.zeppelin.notebook.repo.NotebookRepoSync.(NotebookRepoSync.java:62)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at 
org.glassfish.hk2.utilities.reflection.ReflectionHelper.makeMe(ReflectionHelper.java:1356)
    at org.jvnet.hk2.internal.ClazzCreator.createMe(ClazzCreator.java:248)
    at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:342)
    at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:463)
    at 
org.glassfish.hk2.utilities.ImmediateContext.findOrCreate(ImmediateContext.java:111)
    at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2102)
    at 
org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:93)
    at 
org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:679)
    at 
org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:54)
    at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:188)
    at 
org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:205)
    at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:334)
    at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:463)
    at 
org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:59)
    at 
org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:47)
    at 
org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:74)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at 
org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture.run(Cache.java:131)
    at org.glassfish.hk2.utilities.cache.Cache.compute(Cache.java:176)
    at 
org.jvnet.hk2.internal.SingletonContext.findOrCreate(SingletonContext.java:98)
    at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2102)
    at 
org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:93)
    at 
org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:679)
    at 
org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:54)
    at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:188)
    at 
org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:205)
    at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:334)
    at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:463)
    at 
org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:59)
    at 
org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:47)
    at 
org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:74)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at 
org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture.run(Cache.java:131)
    at org.glassfish.hk2.utilities.cache.Cache.compute(Cache.java:176)
    at 
org.jvnet.hk2.internal.SingletonContext.findOrCreate(SingletonContext.java:98)
    at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2102)
    at 
org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:93)
    at 
org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:679)
    at 
org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:54)
    at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:188)
    at 
org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:205)
    at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:334)
    at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:463)
    at 

[jira] [Created] (ZEPPELIN-5988) Bokeh output in IPySpark is not in correct format

[Axel Van Damme (Jira)]

Axel Van Damme created ZEPPELIN-5988:


 Summary: Bokeh output in IPySpark is not in correct format
 Key: ZEPPELIN-5988
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5988
 Project: Zeppelin
  Issue Type: Bug
  Components: pySpark
Affects Versions: 0.10.1
 Environment: Latest Apache Zeppelin compiled from sources
Reporter: Axel Van Damme


I'm using the latest Zeppelin version compile from the source code (Version 
0.11.0-SNAPSHOT)

I'm facing the issue explained in 
https://issues.apache.org/jira/browse/ZEPPELIN-4771

It means that when running a simple Bokeh code with %ipyspark (or even with 
%python.ipython)interpreter, the text output is not correctly formatted.

You can try for example with this example where I did a on purpose typo:

%ipyspark

import numpy as np
from bokeh.plotting import figure, show, output_notebook

output_notebook()

x = np.linspace(-6, 6, 500)
y = 8*np.sin(x)*np.sinc(x)

p = figure(width=800, height=300, title="", tools="",
           toolbar_location=None, match_aspect=True)

p.line(x, ey, color="navy", alpha=0.4, line_width=4)

show(p)

 

then the output is scrabbled like this:
Loading BokehJS ...
 
---
 NameError Traceback (most recent call last) Cell In[40], 
line 12  7 y = 
8*np.sin(x)*np.sinc(x)
  9 p = 
figure(width=800, 
height=300, 
title="", 
tools="",  10 
toolbar_location=None, 
match_aspect=True) ---> 12 
p.line(x, ey, 
color="navy", 
alpha=0.4, 
line_width=4)  14 show(p) 
NameError: name 'ey' is not defined



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Release of new version

[Jongyoul Lee]

Hello,

Sorry for the late reply.

I'm preparing a new release recently but it's taking time because year-end
and new year season.

I will send the vote sooner than later.

Best regards,
Jongyoul

2023년 12월 22일 (금) 15:34, Amin Borjian 님이 작성:

> Hi.
>
> The last release of Zeppelin (0.10.1) was around two year ago (Feb 2022).
> Because of lots of improvements on Zeppelin, it is not good time to make a
> new release?
> Our company is dependent on Spark, which has introduced many new versions
> that are not currently supported by Zeppelin.
>

Meet our keynote speakers and register to Community Over Code EU!

[Ryan Skraba]

[Note: You're receiving this email because you are subscribed to one or
more project dev@ mailing lists at the Apache Software Foundation.]











*
Merge
with the ASF EUniverse!The registration for Community Over Code Europe is
finally open! Get your tickets now and save your spot!
We are happy to announce that we
have confirmed the first featured speakers
!  - Asim Hussain, Executive
Director at Green Software Foundation- Dirk-Willem Van Gulik, VP of Public
Policy at The Apache Software Foundation- Ruth Ikega, Community Lead at
CHAOSS Africa Visit our website
 to learn more about this
amazing lineup.CFP is openWe are looking forward to hearing all you have to
share with the Apache Community. Please submit your talk proposal
 before January 12, 2024.Interested in
boosting your brand?Take a look at our prospectus

and find out the opportunities we have for you. Be one step ahead and book
your room at the hotel venueWe have a special rate for you at the Radisson
Blu Carlton, the hotel that will hold Community Over Code EU. Learn more
about the location and venue 
and book your accommodation. Should you have any questions, please do not
hesitate to contact us. We wish you Happy Holidays in the company of your
loved ones! See you in Bratislava next year!Community Over Code EU
Organizer Committee*

Release of new version

[Amin Borjian]

Hi.

The last release of Zeppelin (0.10.1) was around two year ago (Feb 2022).
Because of lots of improvements on Zeppelin, it is not good time to make a new 
release?
Our company is dependent on Spark, which has introduced many new versions that 
are not currently supported by Zeppelin.

Re: Pruning many versions embedded into Zeppelin to be able to upgrade to Java 17

[Jongyoul Lee]

Hello,

Thank you for your opinion.

I need to explain the previous discussion. In my understanding,
the Zeppelin community has had a conservative policy - which is not an
actual policy but an atmosphere -  to upgrade dependencies including
interpreters. At that time, it seemed reasonable because everything had
been changed a lot so Zeppelin should support multiple versions and should
keep minimum versions to keep the compatibility.

I agree that it has changed recently. Most data platform components provide
the latest version and Zeppelin can follow it. The community, however,
doesn't have much resources to change it. I'm willing to review if someone
tries to change them. In fact, we change the JDK version to 11 recently.

In short, I agree with you and I hope you start to contribute to those
changes one by one.

If you need any help, please let me know.

Best regards,
Jongyoul Lee

2023년 12월 16일 (토) 오후 3:08, Marc Le Bihan 님이 작성:

> Hello,
>
> Reading the message about the 0.11 version being prepared, I downloaded
> the master branch.
>
> Apache Zeppelin should pruned enough to prepare a move allowing it to be
> able to execute in the current active version: Java 17
> Who can execute it, today, with Java 1.8?
> Who has still on its computer Java 1.8, first? And Scala 2.11, and
> Hadoop 2.7, and... ?
>
> What about leaving many of them?
> Leaving all the old versions to 0.10 and lower, and keeping only the
> last one for the next version?
>
> Even the last version of each plugable tool or langage version might be
> currently the most updated already (scala 2.13 is now recommended for
> Spark 3.x, for example, and scala 2.12 is provided). So why bothering
> keeping those preventing Apache Zeppelin to upgrade to Java 17?
>
> What cannot be receive easily (in next months) a version supporting Java
> 17 should be immediately removed, I think. What future does it have?
> It surely blocks other upgrades.
>
> ---
>
> Apache Zeppelin is a nice project that has been helpful for the Java and
> Scala community. It could be again.
> But yet, it is stuck, and it cannot be repaired, I think, if the parts
> that cannot be upgraded aren't removed from it.
>
> Marc Le Bihan



-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

Pruning many versions embedded into Zeppelin to be able to upgrade to Java 17

[Marc Le Bihan]

Hello,

Reading the message about the 0.11 version being prepared, I downloaded 
the master branch.


Apache Zeppelin should pruned enough to prepare a move allowing it to be 
able to execute in the current active version: Java 17

Who can execute it, today, with Java 1.8?
Who has still on its computer Java 1.8, first? And Scala 2.11, and 
Hadoop 2.7, and... ?


What about leaving many of them?
Leaving all the old versions to 0.10 and lower, and keeping only the 
last one for the next version?


Even the last version of each plugable tool or langage version might be 
currently the most updated already (scala 2.13 is now recommended for 
Spark 3.x, for example, and scala 2.12 is provided). So why bothering 
keeping those preventing Apache Zeppelin to upgrade to Java 17?


What cannot be receive easily (in next months) a version supporting Java 
17 should be immediately removed, I think. What future does it have?

It surely blocks other upgrades.

---

Apache Zeppelin is a nice project that has been helpful for the Java and 
Scala community. It could be again.
But yet, it is stuck, and it cannot be repaired, I think, if the parts 
that cannot be upgraded aren't removed from it.


Marc Le Bihan

[jira] [Created] (ZEPPELIN-5987) release notes missing for last few releases

[PJ Fanning (Jira)]

PJ Fanning created ZEPPELIN-5987:


 Summary: release notes missing for last few releases
 Key: ZEPPELIN-5987
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5987
 Project: Zeppelin
  Issue Type: Improvement
Reporter: PJ Fanning


https://zeppelin.apache.org/download.html has a link for the 0.10.1 release but 
it is broken.

Likewise - 0.10.0

https://zeppelin.apache.org/releases/ - 0.9.0 is the last release with release 
notes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5986) Re-enable Junit 5 integration tests by upgrading maven plugins

[Cheng Pan (Jira)]

Cheng Pan created ZEPPELIN-5986:
---

 Summary: Re-enable Junit 5 integration tests by upgrading maven 
plugins
 Key: ZEPPELIN-5986
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5986
 Project: Zeppelin
  Issue Type: Test
Reporter: Cheng Pan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5985) Remove global scala-* profiles

[Cheng Pan (Jira)]

Cheng Pan created ZEPPELIN-5985:
---

 Summary: Remove global scala-* profiles
 Key: ZEPPELIN-5985
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5985
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Cheng Pan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5984) Upgrade scalatest to 3.2.15 in Cassandra module

[Cheng Pan (Jira)]

Cheng Pan created ZEPPELIN-5984:
---

 Summary: Upgrade scalatest to 3.2.15 in Cassandra module
 Key: ZEPPELIN-5984
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5984
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Cheng Pan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5983) Upgrade to Node 16

[Cheng Pan (Jira)]

Cheng Pan created ZEPPELIN-5983:
---

 Summary: Upgrade to Node 16
 Key: ZEPPELIN-5983
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5983
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Cheng Pan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5982) Merge flink-scala-parent module into flink-scala-2.12

[Cheng Pan (Jira)]

Cheng Pan created ZEPPELIN-5982:
---

 Summary: Merge flink-scala-parent module into flink-scala-2.12
 Key: ZEPPELIN-5982
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5982
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Cheng Pan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5981) Cannot cancel paragraph

[Yunseong Hwang (Jira)]

Yunseong Hwang created ZEPPELIN-5981:


 Summary: Cannot cancel paragraph
 Key: ZEPPELIN-5981
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5981
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.11.0
Reporter: Yunseong Hwang


Inside an open zeppelin notebook, after running a paragraph by clicking the 
play icon button, canceling the running paragraph by clicking the pause icon 
button (or the Ctrl+Option+C shortcut) does not interrupt the running process 
and cancel the paragraph.

I've checked that CANCEL_PARAGRAPH message gets well passed through the 
websocket connection but server was somehow completely ignoring the message.

After some more investigation, I've found that the reason for that was the 
Paragraph's jobAbort() method, which does nothing due to the null interpreter 
member.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5980) Merge zeppelin-display into spark-interperter

[Cheng Pan (Jira)]

Cheng Pan created ZEPPELIN-5980:
---

 Summary: Merge zeppelin-display into spark-interperter
 Key: ZEPPELIN-5980
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5980
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Cheng Pan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5979) Support and use Python 3.9 in default

[Cheng Pan (Jira)]

Cheng Pan created ZEPPELIN-5979:
---

 Summary: Support and use Python 3.9 in default
 Key: ZEPPELIN-5979
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5979
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Cheng Pan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (ZEPPELIN-5978) Remove support for old Flink versions

[Cheng Pan (Jira)]

Cheng Pan created ZEPPELIN-5978:
---

 Summary: Remove support for old Flink versions
 Key: ZEPPELIN-5978
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5978
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Cheng Pan






--
This message was sent by Atlassian Jira
(v8.20.10#820010)