Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
For backward compatibility, we should support in case that users run a paragraph with legacy way like using %interpreterSetting.group. For example, if users' settings' name are spark-prod and spark-dev, user can run with %spark with selecting one of interpreterSetting, but in a new version, user cannot run a paragraph with %spark even though they bind all of spark interpreter including spark-prod and spark-dev. It is proper behaviour for new one, but we need to support old way in order to move user experience smoothly from old to new.
Attachments
Issue Links
- links to