[
https://issues.apache.org/jira/browse/DLAB-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174193#comment-17174193
]
Vira Vitanska commented on DLAB-1813:
-------------------------------------
*Closed:*
Commit ID e32996b822f25d43c312e8504e71d6c2a927e3fe.
> [Branch-515][AWS][Jupyter] :Playbooks
> Flights_data_Visualization_Python2/python3 run with error
> ------------------------------------------------------------------------------------------------
>
> Key: DLAB-1813
> URL: https://issues.apache.org/jira/browse/DLAB-1813
> Project: Apache DLab
> Issue Type: Bug
> Reporter: Vira Vitanska
> Assignee: Mykola Bodnar
> Priority: Major
> Labels: AWS, Debian, DevOps
> Attachments: Azure Jupyter Flights_data_Visualization_Python3.png,
> Azure Jupyter local flight visualization py2.png,
> Flights_data_Visualization_Python2-Spark-local.png,
> Flights_data_Visualization_Python3- local.png,
> Flights_data_Visualization_Pythonr-emr.png,
> GCP-dp13-Flights_data_Visualization_Python2.jpg,
> Verified-AWS-Spark-Flight-Preparation-py3.jpg,
> Verified-AWS-Spark-Flight-Preparation-py3.txt,
> Verified1-AWS-Spark-Floght-visualization-Py2.jpg,
> Verified1-aWS-Spark-Flight-visualization-Py2.txt, logs3
>
>
> This bug was found for local and remote (for EMR, for spark cluster did not
> tested, because it was a bug with spark cluster creation) kernels
> *Preconditions:*
> 1. Playbook Flights_data_preperation_Python2/Python3 were run on Jupyter
> *Steps to reproduce:*
> 1. Run Playbooks Flights_data_Visualization_Python2/python3 on Jupyter
> *Actual result:*
> 1. Playbooks run with error 'Unsupported class file major version 55'
> *Expected result:*
> # Playbooks run successful
> *Flights_data_Visualization (AWS)*
> ||Python2 (local)|{color:#de350b}error with running
> playbook{color}|*{color:#00875a}verified{color}* (01/062020) |
> ||Python3 (local)|{color:#de350b}error with running
> playbook{color}|{color:#00875a}*verified* {color}(01/06/2020)|
> ||Python2 (EMR
> 5.30)|{color:#4c9aff}Blocked{color}|{color:#00875a}*verified*{color}
> (02/06/2020)|
> ||Python3 (EMR
> 5.30)|{color:#4c9aff}Blocked{color}|{color:#00875a}*verified*{color}
> (02/06/2020)|
> ||Python2 (EMR
> 6.0.0)|{color:#4c9aff}Blocked{color}|{color:#00875a}*verified*{color}
> (03/06/2020)|
> ||Python3
> (EMR)|{color:#4c9aff}Blocked{color}|{color:#00875a}*verified*{color}
> (03/06/2020)|
> ||Python2 (Spark)|{color:#4c9aff}Blocked{color}|*{color:#de350b}runs with
> error{color}* (02/06/20)|
> ||Python3 (Spark)|{color:#4c9aff}Blocked{color}|{color:#de350b}*runs with
> error* {color}(02/06/20)|
>
> ----
>
> *Flights_data_Visualization (GCP)*
> ||Python2 (local)|{color:#de350b}error with running
> playbook{color}|*{color:#00875a}verified{color}* (10/06/2020)|
> ||Python3 (local)|{color:#de350b}error with running
> playbook{color}|{color:#00875a}*verified* {color}(10/06/2020)|
> ||Python2 (DP1.3)|{color:#de350b}error with running playbook - another
> error-view screenshot{color}|*{color:#00875a}verified{color}* (11/06/2020)|
> ||Python3 (DP1.3)|{color:#de350b}error with running playbook - another error
> -view screenshot{color}|{color:#00875a}*verified*{color} (11/06/2020)|
> ||Python2 (DP1.4)|{color:#de350b}error with running
> playbook{color}|*{color:#00875a}verified{color}* (11/06/2020)|
> ||Python3 (DP1.4)|{color:#de350b}error with running
> playbook{color}|*{color:#00875a}verified{color}* (11/06/2020)|
> ||Python2 (DP1.5 ubuntu)|-|*{color:#00875a}verified{color}* (16/06/2020)|
> ||Python3 (DP1.5 ubuntu)|- |*{color:#403294}blocked{color}* (on prepare
> stage) (16/06/2020)|
> ||Python2 (Spark)|{color:#de350b}error with running
> playbook{color}|{color:#00875a}*verified*{color} (11/06/2020)|
> ||Python3 (Spark)|{color:#de350b}error with running
> playbook{color}|*{color:#00875a}verified{color}* (11/06/2020)|
>
> ----
> (i) *This bug is not reproduced for GCP* (11/06/2020).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
