Closed jonded94 closed 1 day ago
If we want to allow creating Row
s outside the module, would it be better to add a public new()
to the Row
API? (And maybe get rid of make_row
?)
cc @alamb @tustvold
Implemented an alternative PR which does remove make_row
entirely and creates a new
method. https://github.com/apache/arrow-rs/pull/6763
Let me know whichever approach you prefer :) This unfortunately currently blocks a bit my work (I have some manual steps where I explicitly modify & create new Row
instances and can't do that right now), so I'm happy to have quick progress here.
Which issue does this PR close?
Closes https://github.com/apache/arrow-rs/issues/6761
Rationale for this change
parquet::record::make_row
was not exposed to users, leaving them no option to createparquet::record::Row
objects themselfes.What changes are included in this PR?
parquet::record::make_row
is exposed publicy.