[ 
https://issues.apache.org/jira/browse/LIVY-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gyorgy Gal updated LIVY-857:
----------------------------
    Fix Version/s: 0.10.0
                       (was: 0.9.0)

This issue has been moved to the 0.10.0 release as part of a bulk update. If 
you feel this is moved out inappropriately, feel free to provide justification 
and reset the Fix Version to 0.9.0.

> In k8s, Interactive session's library on spark 3.0.2, classes in packages 
> cannot be imported
> --------------------------------------------------------------------------------------------
>
>                 Key: LIVY-857
>                 URL: https://issues.apache.org/jira/browse/LIVY-857
>             Project: Livy
>          Issue Type: Bug
>          Components: RSC
>    Affects Versions: 0.7.0, 0.8.0
>            Reporter: Keunhyun Oh
>            Priority: Major
>             Fix For: 0.10.0
>
>
> In my k8s enviroment, Interactive session's library on spark 3.0.2, classes 
> in packages are cannot imported.
>  
> I will try to use livy binary packages below,
> 1) 0.7.0: binaries in AWS EMR 6.3.0 (for using scala 2.12)
> 2) 0.8.0-SNAPSHOT: 
> [https://github.com/jahstreet/incubator-livy]
> 3) spark 3.0.2: 
> - using client mode: [https://github.com/apache/spark/tree/v3.0.2]
> - using cluster mode:  [https://github.com/apache/spark/pull/32397]
>  
> ln jupyter notebook with spark magic, configure is that
> {code:java}
> %%configure -f
> {...
>  ...
>  "conf": {"spark.jars.packages": "mypackages" }
>  ...
> }{code}
>  
> The error is raised when importing some class,
> {code:java}
> import com.mypackage.test{code}
> {code:java}
> An error aws encounted:
> <console>:23:error: object mypackage is not a member of package com
>     import com.mypackage.test{code}
>  
> However, it is no problem that calling class by name 
> {code:java}
> Class.forName(com.mypackage.test){code}
>  
> It is only occured in livy interactive session.
> livy batch, spark-submit and spark-shell  have no problem about it.



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

Reply via email to