Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[df] Force only one RNTuple name in distributed scheduling #14895

Merged
merged 1 commit into from
Mar 7, 2024
Merged

[df] Force only one RNTuple name in distributed scheduling #14895

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion bindings/experimental/distrdf/python/DistRDF/HeadNode.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -826,11 +826,14 @@ def __init__(self, backend: BaseBackend, npartitions: Optional[int], localdf: RO

self.mainntuplename = args[0]
self.inputfiles = args[1]
# Keep this in accordance with the implementation of TTree for now
self.subnames = [self.mainntuplename] * len(self.inputfiles)

def _build_ranges(self) -> List[Ranges.DataRange]:
# """Build the ranges for this dataset."""
return Ranges.get_ntuple_ranges(self.subnames, self.inputfiles, self.npartitions, self.exec_id)
# For the moment, we explicitly pass only one "subname", since there is
# only one name possible for the whole RNTuple
return Ranges.get_ntuple_ranges(self.mainntuplename, self.inputfiles, self.npartitions, self.exec_id)

def _generate_rdf_creator(self) -> Callable[[Ranges.DataRange], TaskObjects]:
"""
Expand Down
Loading