Add runtime profile loading for simulation configuration #27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Enables loading task properties (model, runId, runLogFileName, runDescription) from profile-specific properties files at runtime. - Add profile property: -Datscale.closedsimulation.profile=<profile_name> - Loads <profile_name>_systems.properties for all task settings - Property lookup order: system props -> profile file -> systems.properties - Throws exception if required property not found Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…sed config - Add JdbcSimulationExecutor for running JDBC-only simulations - Add XmlaSimulationExecutor for running XMLA-only simulations - Add ProfilePropertyLoader utility for loading properties from filesystem or classpath - Create example profile properties files (example_jdbc_profile.properties, example_xmla_profile.properties) - Revert ClosedStepSequentialSimulationExecutor to original hardcoded configuration - Rename and update documentation to RUNTIME_PROFILE_OVERRIDES.md Configuration via -Datscale.profileFile=<filename> with properties: - atscale.task.name, atscale.task.model, atscale.task.runId - atscale.task.runLogFileName, atscale.task.runDescription Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Fix Javadoc in JdbcSimulationExecutor and XmlaSimulationExecutor - Update example_systems.properties comment to reference new executors Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add getProfileProperties() method to ProfilePropertyLoader that returns HashMap<String, String> - Update JdbcSimulationExecutor and XmlaSimulationExecutor to use setAdditionalProperties() instead of setAlternatePropertiesFileName() - This provides better type safety and direct property access for task configuration - Add /.metals to .gitignore for Scala IDE files Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
stevejhall
approved these changes
Feb 10, 2026
Collaborator
stevejhall
left a comment
stevejhall
left a comment
There was a problem hiding this comment.
Change for additional properties usage looks like it completes the goal.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
ProfilePropertyLoaderutility for loading configuration from external properties files at runtimeJdbcSimulationExecutorandXmlaSimulationExecutorfor profile-based simulation execution-Datscale.profileFile=<path>HashMap<String, String>for better type safetyFeatures
-Dflags) override file valuesHashMap<String, String>viasetAdditionalProperties()Implementation Details
ProfilePropertyLoader.getProfileProperties()returnsHashMap<String, String>for type safetysetAdditionalProperties()to directly pass configuration map to tasksPropertiesobject usingstringPropertyNames()Usage
🤖 Generated with Claude Code