Skip to content

Spark options set by the user are not handled properly #431

Open

Description

@razvan

Affected Stackable version

all

Affected Apache Spark-on-Kubernetes version

all

Current and expected behavior

Spark properties that are set by both the user via spec.sparkConf and the operator are not merged properly.

Example: users that need to set Java proxy settings via spark.driver.extraJavaOptions cannot do so without overriding the same property set by the operator.

Possible solution

No response

Additional context

No response

Environment

No response

Would you like to work on fixing this bug?

None

Activity

  1. lfrancke commented on Aug 7, 2024

    @lfrancke
    Member

    Reported on Discord

  2. sbernauer commented on Aug 15, 2024

    @sbernauer
    Member

    To me personally this sounds like expected behavior. The fields docs state

    A map of key/value strings that will be passed directly to spark-submit.

    which it seems to do.

    It think it's a very hard problem to correctly merge all the Spark properties in the world but let's see :)

    I personally would consider this a feature request to make it easier to merge stuff from the user onto the operator generated ones - which sounds like a nice quality of live feature - if possible.

  3. sbernauer commented on Aug 15, 2024

    @sbernauer
    Member

    Reported on Discord

    I could not find it. Can you please paste the report here, so we can understand what exactly is going and maybe also conclude this is a bug?

  4. lfrancke commented on Sep 16, 2024

    @lfrancke
    Member

    I can't find it either right now, sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions