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

Akmal Chaudhri updated IGNITE-8296:
-----------------------------------
    Description: 
# The Spark Scala DataFrames code examples are in the wrong directory. They 
should be moved to the correct directory structure.
 # The Spark Scala DataFrames code examples should follow the naming convention 
used for other Scala code examples and be prefixed with "Scalar".

  was:
# The Spark Scala code examples are in the wrong directory. They should be 
moved to the correct directory structure.
 # The Spark Scala code examples should follow the naming convention used for 
other Scala code examples and be prefixed with "Scalar".

        Summary: Move Spark Scala DataFrames code examples to correct directory 
and prefix with "Scalar" to follow convention used with other Scala examples   
(was: Move Spark Scala code examples to correct directory and prefix with 
"Scalar" to follow convention used with other Scala examples )

> Move Spark Scala DataFrames code examples to correct directory and prefix 
> with "Scalar" to follow convention used with other Scala examples 
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-8296
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8296
>             Project: Ignite
>          Issue Type: Improvement
>          Components: spark
>    Affects Versions: 2.4
>            Reporter: Akmal Chaudhri
>            Assignee: Akmal Chaudhri
>            Priority: Minor
>             Fix For: 2.5
>
>
> # The Spark Scala DataFrames code examples are in the wrong directory. They 
> should be moved to the correct directory structure.
>  # The Spark Scala DataFrames code examples should follow the naming 
> convention used for other Scala code examples and be prefixed with "Scalar".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to