Skip to content

Commit

Permalink
[df] Force only one RNTuple name in distributed scheduling
Browse files Browse the repository at this point in the history
  • Loading branch information
vepadulano committed Mar 7, 2024
1 parent fa550ec commit bbd0dc2
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion bindings/experimental/distrdf/python/DistRDF/HeadNode.py
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

0 comments on commit bbd0dc2

Please sign in to comment.