-
Notifications
You must be signed in to change notification settings - Fork 374
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.
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
Only override the arrow1 versions of the Loggable trait #8604
Conversation
Web viewer built successfully. If applicable, you should also test it:
Note: This comment is updated whenever you push a commit. |
// TODO(cmc): We use the extended type here because we rely on it for formatting. | ||
Ok(StructArray::new(datatype, values, validity).boxed()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@teh-cmc this will surely cause a regression, but I don't know where.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(I haven't reviewed the rest of the PR so I might be lacking context)
This is the one exception where we really really want to keep the extension around, otherwise printing any chunk becomes awful, which makes day-to-day life very hard.
Any reason you cannot keep it around?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no extended types in arrow-rd
:
I can set ARROW:extension:name
: rerun.datatypes.TUID
in the metadata
on the fields (but which field?), but I need some way to test that I'm not breaking anything. I don't know where we rely on this.
AFAICT we use it when displaying a ChunkId
or RowId
in the UI… which I'm not sure we do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Manually adding an ARROW:extension:name
in the TransportChunk
glue seems like the right solution yes.
The best way to test for this is Command Palette > Print datastore
. Right now your PR doesn't break it (probably because that still goes through arrow2?), so we can see about that later.
@@ -23,115 +23,113 @@ use crate::{Archetype, ComponentBatch, LoggableBatch}; | |||
/// which makes it possible to work with lists' worth of data in a generic fashion. | |||
pub trait Loggable: 'static + Send + Sync + Clone + Sized + SizeBytes { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I moved around the functions to group them better (arrow2 stuff at the end). Sorry.
740bd2e
to
a324a3b
Compare
23cbb36
to
026b310
Compare
@rerun-bot full-check |
Started a full build: https://github.com/rerun-io/rerun/actions/runs/12658242886 |
Related
re_arrow2
toarrow
#3741What
All the arrow2-functions on
trait Loggable
now defer to the arrow1 implementations, and all implementations only override the arrow1-trait functions.