Hey, Is it possible to see all the configs availa...
# hamilton-help
s
Hey, Is it possible to see all the configs available for a DAG? For example, I want to see all possible `last_run`config options. When I pass the config (in green), the DAG is nice to tell me which
last_run
is being used and its reflected by the function getting used
_with_filter_run_date
. However, for documentation purposes, how would you suggest amending so that all
last_run
config options are visible in the DAG? Is this possible?
Copy code
@extract_fields({
    "child_process_run_id": int,
    "child_process_completed_at": pd.Timestamp,
})
@pipe_input(
    step(_filter_run_bom).when(last_run="bom"),
    step(_filter_run_latest).when(last_run="last"),
    step(_filter_run_date, completion_date=source("completion_date")).when(last_run="completion_date"),
)
def child_process_run_info(
    child_process_runs: pd.DataFrame, 
    child_rec_process_code: str, 
    completion_date: Optional[str] = None
) -> Dict[int, pd.Timestamp]:
    """Return run id for process from `last_run` logic."""
Slack Conversation
s
We haven't officially built anything to expose this.
That is, Hamilton currently doesn't have an interface to return what config values are possible/ needed.
Could you create an issue if this would help you please?
s
Ok thanks sir, will do
🙏 1
Does the
executors.SynchronousLocalTaskExecutor()
simply allow for the syntactic sugar of
Parallelizable/Collect
or does it actually process in parallel? If not, would you recommend the
MultiThreadingExecutor()
instead?
s
Not in parallel. Yes try the multithreading one
s
Ok thanks. So if I’m debugging something I should use the Synchronous one since it might be more compatible with the PdbDebugger hook? IIRC, it wasnt compatible for something to do with parallelism? Do you happen to know what I’m remembering? Hah
s
🤔 yes maybe? Sounds plausible.