@davidanthoff what’s the relationship between tabletraits.jl and tables.jl? Edit: and interabletables.jl

Tables.jl was started when @davidanthoff and I had a chance to hack together at JuliaCon 2018 in London for several hours on how we could join forces with TableTraits.jl/IterableTables.jl & DataStreams.jl (it’s better for everyone if there can be a single, standard tables interface). Tables.jl was t…

Thank you for this clarification…Tables.jl sounds very promising and it does make sense for there to be one common interface/ So will the queryverse be transitioning to Tables.jl ? Also how does Tables.jl handle non random access or even iterable structures like distributed tables? What about nest…

[image] TextParse.jl is fast again Thank you for this clarification…Tables.jl sounds very promising and it does make sense for there to be one common interface/ So will the queryverse be transitioning to Tables.jl ? Ultimately that’s up to @davidanthoff ; he’s made excellent contributions to ho…

I do not plan to migrate the Queryverse.jl to Tables.jl . I’m not on board with a number of important design decisions in Tables.jl (*), and more generally don’t see a reason to start with yet another table interface for Queryverse.jl at this point. TableTraits.jl has been around for a long time, wit…

Understood. Can you elaborate on the interop story?

[image] davidanthoff: I do not plan to migrate the Queryverse.jl to Tables.jl . Well, this is disappointing for the data community. The entire purpose of Tables.jl is as a community-driven approach to a unified table interface to make data formats & table types easier to integrate across the…

[image] quinnj: I do not plan to migrate the Queryverse.jl to Tables.jl . Well, this is disappointing for the data community. The entire purpose of Tables.jl is as a community-driven approach to a unified table interface to make data formats & table types easier to integrate across the ecosy…

[image] quinnj: e we’re seeing with StatsModels.jl . It’s non-ideal, for example, to expect packages who want to do table s Query.jl will keep it’s front end dplyr like API, the discussion is on what the backend should look like. I also completely concur with @quinnj about having a unified i…

[image] swissr: I don’t understand this. Why should Queryverse.jl migrate to Tables.jl? Isn’t the goal of Queryverse to provide an API similar to R Tidyverse, how could it change the API? As @datnamer mentioned, this wouldn’t affect the user-facing API of Query.jl at all. [image] swissr: …

Thank you quinnj and datnamer for the detailed answers!

Tables.jl vs TableTraits.jl (was TextParse.jl is fast again)

Specific Domains Data

Topic		Replies	Views
Tables.jl: a table interface for everyone Data tables	19	10947	November 19, 2018
Common API for tabular data backends Data	44	2909	August 28, 2020
DataTables or DataFrames? Data question	32	15666	November 19, 2018
Random access to rows of a table Machine Learning	27	2277	March 14, 2022
2024: Tables.jl vs TableTraits.jl/IterableTables.jl? General Usage question	1	265	February 21, 2024

Tables.jl vs TableTraits.jl (was TextParse.jl is fast again)

Related topics