Uploaded image for project: 'SW'
  1. SW-571

In PySparkling, getOrCreate(spark) still incorrectly complains that we should use spark session

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.18, 2.1.17, 2.2.3
    • Component/s: None
    • Labels:
      None
    • CustomerVisible:
      No

      Description

      The issue is that we still use spark context internally in pysparkling, sending it to the java/scala backend where this warning is printed.

      This can be easily fixed by properly using sparksession instead of spark context in pysparkling internals.

        Attachments

          Activity

            People

            • Assignee:
              Kuba Jakub Hava
              Reporter:
              Kuba Jakub Hava
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Stride room