[
https://issues.apache.org/jira/browse/SPARK-34243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naman Nigam updated SPARK-34243:
--------------------------------
Description:
Trying to derive the automatic module name for any of the spark related
artifacts currently fails with the following error.
{\{naman.nigam jar
--file=/Users/naman.nigam/.m2/repository/org/apache/spark/spark-core_2.12/3.1.0/spark-core_2.12-3.1.0.jar
--describe-module}}
{{Unable to derive module descriptor for:
/Users/naman.nigam/.m2/repository/org/apache/spark/spark-core_2.12/3.1.0/spark-core_2.12-3.1.0.jar}}{{spark.core.2.12:
Invalid module name: '2' is not a Java identifier}}
I was hoping there could be an improvement in this direction such that the
artifacts could be used in the modularised applications even if they are not
themself modularised.
This relates to a previous bug reported under
https://issues.apache.org/jira/browse/SPARK-23543, but it has been
unfortunately closed as Incomplete and there seems no other way to track the
progress that Spark is planning to make in this direction.
was:
Trying to derive the automatic module name for any of the spark related
artifacts currently fails with the following error.
{{naman.nigam jar
--file=/Users/naman.nigam/.m2/repository/org/apache/spark/spark-core_2.12/3.1.0/spark-core_2.12-3.1.0.jar
--describe-module}}
{{Unable to derive module descriptor for:
/Users/naman.nigam/.m2/repository/org/apache/spark/spark-core_2.12/3.1.0/spark-core_2.12-3.1.0.jar}}{{spark.core.2.12:
Invalid module name: '2' is not a Java identifier}}
I was hoping there could be an improvement in this direction such that the
artifacts could be used in the modularised applications even if they are not
themself modularised.
> Update the spark libraries to expose Java module names
> ------------------------------------------------------
>
> Key: SPARK-34243
> URL: https://issues.apache.org/jira/browse/SPARK-34243
> Project: Spark
> Issue Type: Improvement
> Components: Java API
> Affects Versions: 3.0.1
> Environment: As an environment, making use of a `module-info.java`
> with the application based out of Spark would fail to compile for the lack of
> underlying packages being visible anymore to the main application code.
> Reporter: Naman Nigam
> Priority: Major
>
> Trying to derive the automatic module name for any of the spark related
> artifacts currently fails with the following error.
> {\{naman.nigam jar
> --file=/Users/naman.nigam/.m2/repository/org/apache/spark/spark-core_2.12/3.1.0/spark-core_2.12-3.1.0.jar
> --describe-module}}
> {{Unable to derive module descriptor for:
> /Users/naman.nigam/.m2/repository/org/apache/spark/spark-core_2.12/3.1.0/spark-core_2.12-3.1.0.jar}}{{spark.core.2.12:
> Invalid module name: '2' is not a Java identifier}}
>
> I was hoping there could be an improvement in this direction such that the
> artifacts could be used in the modularised applications even if they are not
> themself modularised.
>
> This relates to a previous bug reported under
> https://issues.apache.org/jira/browse/SPARK-23543, but it has been
> unfortunately closed as Incomplete and there seems no other way to track the
> progress that Spark is planning to make in this direction.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
