Skip to content

ZEPPELIN-3517 Remove zeppelin.pyspark.python in PySparkInterpreter#2993

Closed
zjffdu wants to merge 1 commit intoapache:masterfrom
zjffdu:ZEPPELIN-3517
Closed

ZEPPELIN-3517 Remove zeppelin.pyspark.python in PySparkInterpreter#2993
zjffdu wants to merge 1 commit intoapache:masterfrom
zjffdu:ZEPPELIN-3517

Conversation

@zjffdu
Copy link
Copy Markdown
Contributor

@zjffdu zjffdu commented May 31, 2018

What is this PR for?

zeppelin.pyspark.python should be removed as it is zeppelin specific property, and only affect the driver, but not on executor. So we should use spark property instead.

What type of PR is it?

[Bug Fix]

Todos

  • - Task

What is the Jira issue?

How should this be tested?

  • CI pass

Screenshots (if appropriate)

Questions:

  • Does the licenses files need update? No
  • Is there breaking changes for older versions? No
  • Does this needs documentation? No

@r-kamath
Copy link
Copy Markdown
Member

LGTM

Copy link
Copy Markdown
Member

@felixcheung felixcheung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not just map it to PYSPARK_DRIVER_PYTHON or PYSPARK_PYTHON

@zjffdu
Copy link
Copy Markdown
Contributor Author

zjffdu commented Jun 1, 2018

@felixcheung The only place to do mapping is in zeppelin server side, and I it is better not to put any interpreter specific login in zeppelin server side. And I think it's better for zeppelin to use the same configuration as spark instead of introducing zeppelin specific configuration.

@felixcheung
Copy link
Copy Markdown
Member

felixcheung commented Jun 1, 2018 via email

@zjffdu
Copy link
Copy Markdown
Contributor Author

zjffdu commented Jun 1, 2018

Thanks @felixcheung . I still think it is better to remove it. As it is difficult to deprecate this and let users to aware of that. Zeppelin is a notebook instead of library. If we don't remove it and just deprecate it in documentation, I believe most of users won't be know that and would continue to use it and may ask question in user mail list why they hit python version mismatch issue between driver and executors.

@asfgit asfgit closed this in b06e97c Jun 7, 2018
mckartha pushed a commit to syntechdev/zeppelin that referenced this pull request Aug 9, 2018
### What is this PR for?
`zeppelin.pyspark.python` should be removed as it is zeppelin specific property, and only affect the driver, but not on executor. So we should use spark property instead.

### What type of PR is it?
[Bug Fix]

### Todos
* [ ] - Task

### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-3517

### How should this be tested?
* CI pass

### Screenshots (if appropriate)

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No

Author: Jeff Zhang <[email protected]>

Closes apache#2993 from zjffdu/ZEPPELIN-3517 and squashes the following commits:

24dafa1 [Jeff Zhang] ZEPPELIN-3517. Remove zeppelin.pyspark.python in PySparkInterpreter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants