Add ParquetObjectReader::with_runtime
#6612
Conversation
github-actions
bot
added
parquet
| #[tokio::test] | ||
| // We need to mark this with the `target_has_atomic` because the spawned_tasks_count() fn is | ||
| // only available for that cfg | ||
| #[cfg(all(target_has_atomic = "64", tokio_unstable))] |
There was a problem hiding this comment.
I wonder if we could instead create a runtime with IO / blocking threads disabled and use that to determine that the IO was spawned to a different runtime?
There was a problem hiding this comment.
I don't think that would work. I'm not certain why, but ParquetObjectReader seems to work fine regardless of whether or not IO is 'enabled' on its runtime. I was able to change the tests so they don't rely on tokio_unstable anymore and (I think) still show what we want them to show, so I'll push that in a minute.
There was a problem hiding this comment.
Thanks @itsjunetime -- this is looking very good. I think we need to also move get_metadata to spawn
Otherwise I have a few other suggestions, but this one is looking very close
|
|
||
| assert_ne!(current_id, other_id); | ||
|
|
||
| tokio::runtime::Handle::current().spawn_blocking(move || drop(rt)); |
There was a problem hiding this comment.
Can you also add unit tests for each of the three APIs in ParquetObjectReader that spawn is used?
get_bytesget_byte_rangesget_metadata?
Co-authored-by: Andrew Lamb <[email protected]>
- Remove outdated comment about target_has_atomic - Add test to verify reader fails when spawned on a shutdown runtime
parquet/src/errors.rs
Outdated
| @@ -107,6 +107,13 @@ impl From<str::Utf8Error> for ParquetError { | |||
| } | |||
| } | |||
|
|
|||
| #[cfg(test)] | |||
| impl From<std::convert::Infallible> for ParquetError { | |||
There was a problem hiding this comment.
This is a nice improvement too. Thank you. Maybe it is worth adding publically as well
There was a problem hiding this comment.
I'm not sure about this, the whole point of infallible is that it can't be constructed and so doesn't need to be handled
There was a problem hiding this comment.
Well, it can't be constructed, but it often does need to be "handled" (aka to transform a Result<.., Infallible> to Result<.., Error> type expected by an API)
I don't feel strongly about this particular code.
There was a problem hiding this comment.
aka to transform a Result<.., Infallible> to Result<.., Error> type expected by an API)
Right but this is a little funky, because it then makes code look more fallible than it is. Often you can use an infallible version of the API, i.e. into() instead of try_into(), but sometimes you do have to either unwrap() or let _ = ...
FWIW Rust 1.82 gives us a very nice way to handle this, but I'm not sure whether our MSRV policy covers tests.
let Ok(value) = expression();
| let current_id = std::thread::current().id(); | ||
|
|
||
| let other_id = reader | ||
| .spawn(|_, _| async move { Ok::<_, Infallible>(std::thread::current().id()) }.boxed()) |
There was a problem hiding this comment.
| .spawn(|_, _| async move { Ok::<_, Infallible>(std::thread::current().id()) }.boxed()) | |
| .spawn(|_, _| async move { Ok::<_, ParquetError>(std::thread::current().id()) }.boxed()) |
Would remove the need for the std::convert::Infallible conversion
There was a problem hiding this comment.
I had this repo checked out and in the editor, so I just made this change to accelerate getting this PR in in 8d24cd7
It results in a nice simplification
|
Thanks again @itsjunetime and @tustvold |
Which issue does this PR close?
Closes #6248
What changes are included in this PR?
This PR works on top of #6249 to add a test for the new
with_runtimefn, as well as changing the signature of thespawnfunction slightly to avoid an extra re-boxing when a runtime is set.This also fixes a few things that
clippywas complaining about.Rationale for this change
See #6248 for the API addition.
With regard to the test, I felt like this is really the only test we'd want for this feature - we just want to make sure that the runtime is actually being used by
ParquetObjectReader. We can't make any guarantees about how it actually performs or would work if there's another runtime being used for CPU-bound operations, so all we really want to test is if it is used.Are there any user-facing changes?
No