fix(stepfunctions): DistributedMap ResultWriter correct query language selection

[phuhung273]

Issue # (if applicable)

Close #35403

Reason for this change

• Incorrect template when using StateMachine JSONPath with DistributedMap's ResultWriter with JSONata
• Streamline JSONata migration. Without this fix, the only workaround is switching entire StateMachine to JSONata, requiring too much change.

Description of changes

• DistributedMap add query language validation
• DistributedMap ResultWriter correct query language selection

Description of how you validated changes

Unit + Integ

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[kumvprat]

Thanks for your contribution.

Added a few inline comments

Can you also give me context into the feature flag being used in the test ?
Overall we should test with and without the feature flag being set and check for proper query language setting .

[kumvprat]

Is this something we need to set explicitly ?

What about the case where this feature flag is false ? We need to add tests for that use case as well

[phuhung273]

I believe this is a defect of getResultWriter function

aws-cdk/packages/aws-cdk-lib/aws-stepfunctions/lib/states/distributed-map.ts

Lines 206 to 210 in de261c0

	private getResultWriter(): ResultWriterV2 | ResultWriter | undefined {
	return FeatureFlags.of(this).isEnabled(STEPFUNCTIONS_USE_DISTRIBUTED_MAP_RESULT_WRITER_V2)
	? this.resultWriterV2
	: this.resultWriter;
	}

Currently, to use resultWriterV2 we need 2 steps:

1. Set the flag to true
2. Specify param resultWriterV2: new stepfunctions.ResultWriterV2

I think only step 2 should be enough. But won't change this logic for now.

My intention when first submitting the PR was ignoring unit test for V1 as we're encouraging migration to V2. It is now added anw. Pls have a look.

[kumvprat]

Added a comment in the test changes, apart from that it looks good.

[phuhung273]

Thanks so much for the help @kumvprat

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.