[Feature][config] improve the config parse logic

Search before asking

• I had searched in the feature and found no similar feature requirement.

Description

This sub issue focus on solving the parse logic

• Change path token separator from “.” to “->”".
• Added parseObjectForseatunnel() to parse config objects in input, filter, output for seatunnel.

👉 Change 1 : Change path token separator from “.” to “->”".

config always let the key as path if the key contains ., like following

sink {
  a.b.c.Console {}
}

equivalent to

sink {
  a {
    b {
      c {
        Console {}
      }
    }
  }
}

In fact, it’s not recommend to make these changes, because JSON keys should be enclosed in double quotes, so we can revert these changes.

👉 Change 2 : parseObjectForseatunnel().

The main login of parseObjectForseatunnel is to parse config objects in sources, transforms, sinks for seatunnel.

We can move these changes out of config, and move them to ConfigBuilder

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project’s Code of Conduct

[RickyHuo]

I have saw the draft PR. The seatunnel-config has been replaced with typesafe config.

The reason why we develop seatunnel-config base on typesafe config is that the plugin order of parsed Config is not the same as our configuration when transform section has multiply plugins.

The origin issue is #29, I’m sorry I forget config test at that moment.

We should test those demo:

source {
	
}

transform {
	
	sql {
		sql = "sql1"
	}

	sql {
		sql = "sql2"
	}

	sql {
		sql = "sql3"
	}
}

sink {
	
}

source {
	
}

transform {
	
	sql {
		sql = "sql1"
	}

	json {
		source_field = "xxx"
	}

	sql {
		sql = "sql3"
	}
}

sink {
	
}

[simon824]

Great job ! I’m ok with these two changes, and I will test more cases later.