NVIDIA-Merlin / NVIDIA-Merlin/Transformers4Rec

RuntimeError: CUDF failure at: /__w/cudf/cudf/cpp/src/io/parquet/reader_impl_helpers.cpp:379: Invalid rowgroup index[BUG]

Open
#756 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug status/needs-triage
Dominant language
Python
Stars
1.3k
Forks
165
Avg merge
1m
Merged PRs (30d)
2

Description

Tried to run the tutorial of transformers4rec and i got this error

RuntimeError Traceback (most recent call last)
in

/usr/local/lib/python3.10/dist-packages/transformers/trainer.py in evaluate(self, eval_dataset, ignore_keys, metric_key_prefix)
3005 self._memory_tracker.start()
3006
-> 3007 eval_dataloader = self.get_eval_dataloader(eval_dataset)
3008 start_time = time.time()
3009

16 frames
/usr/local/lib/python3.10/dist-packages/cudf/io/parquet.py in _read_parquet(filepaths_or_buffers, engine, columns, row_groups, use_pandas_metadata, *args, **kwargs)
819 f"following positional arguments: {list(args)}"
820 )
--> 821 return libparquet.read_parquet(
822 filepaths_or_buffers,
823 columns=columns,

parquet.pyx in cudf._lib.parquet.read_parquet()

parquet.pyx in cudf._lib.parquet.read_parquet()

RuntimeError: CUDF failure at: /__w/cudf/cudf/cpp/src/io/parquet/reader_impl_helpers.cpp:379: Invalid rowgroup index

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Transformers4Rec tutorial and follow the traceback through transformers/trainer.py and cudf/io/parquet.py, focusing on the evaluation dataloader and parquet row-group handling. Done means the tutorial's evaluation step completes without the CUDF invalid-rowgroup error, with the failing dataset or compatibility cause identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.