Giter VIP home page Giter VIP logo

Comments (5)

cmdlineluser avatar cmdlineluser commented on June 17, 2024 1

It's happening due to n_field_strategy

Because group_by is returning random order, the length of the first list changes.

df.group_by("a", "b").agg(pl.col("value").bottom_k(3))
# shape: (4, 3)
# ┌─────┬─────┬───────────┐
# │ a   ┆ b   ┆ value     │
# │ --- ┆ --- ┆ ---       │
# │ i64 ┆ str ┆ list[i64] │
# ╞═════╪═════╪═══════════╡
# │ 2   ┆ A   ┆ [99]      │
# │ 2   ┆ B   ┆ [3]       │
# │ 1   ┆ A   ┆ [1, 2]    │
# │ 1   ┆ B   ┆ [4, 98]   │
# └─────┴─────┴───────────┘

df.group_by("a", "b").agg(pl.col("value").bottom_k(3))
# shape: (4, 3)
# ┌─────┬─────┬───────────┐
# │ a   ┆ b   ┆ value     │
# │ --- ┆ --- ┆ ---       │
# │ i64 ┆ str ┆ list[i64] │
# ╞═════╪═════╪═══════════╡
# │ 1   ┆ A   ┆ [1, 2]    │
# │ 2   ┆ B   ┆ [3]       │
# │ 1   ┆ B   ┆ [4, 98]   │
# │ 2   ┆ A   ┆ [99]      │
# └─────┴─────┴───────────┘

You would need n_field_strategy="max_width"

.list.to_struct("max_width", upper_bound=3))

from polars.

cmdlineluser avatar cmdlineluser commented on June 17, 2024 1

Yeah, something similar came up in #15742 recently.

When n is known, it's effectively:

pl.struct(
    field_0 = pl.col("value").list.get(0),
    field_1 = pl.col("value").list.get(1),
    field_2 = pl.col("value").list.get(2)
)

But not having to type all that out seems like it would be useful.

from polars.

kevinli1993 avatar kevinli1993 commented on June 17, 2024

Makes sense now! I guess this means n_field_strategy=first_non_null is only useful when the number of elements is known to be the same.

Maybe (?) not a bug, but we might consider adding a warning to the documentation since it's a surprising consequence.

from polars.

cmdlineluser avatar cmdlineluser commented on June 17, 2024

Yeah - it is a bit of a footgun.

There was a Notes section added with an explanation - but perhaps a Warning should also be added pointing to that section.

from polars.

kevinli1993 avatar kevinli1993 commented on June 17, 2024

Agreed.

Would it make sense for .to_struct to accept an argument exact=n, so that the resulting final struct has exactly n fields (filling with null when necessary)?

It would behave similar to str.split and str.split_exact. (Maybe we could create a new function .to_struct_exact.)

from polars.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.