Daft Version Compatibility

Oct 13, 2025 by talynt.org 120 views

Introduction

Daft is a Python library used for data manipulation and analysis. It provides a simple and efficient way to work with data, including data transformation, filtering, and aggregation. However, with the latest version of Daft (0.4.7), a known issue has been reported where wildcard select on a struct does not work as expected. In this article, we will explore this issue, provide a sample code to reproduce the problem, and discuss the expected behavior.

Describe the Bug

The bug is related to the wildcard select functionality on a struct in the latest version of Daft. When trying to select all columns from a struct using the attributes.* syntax, an exception is raised. The exception message indicates that the column attributes.* is an outer column but does not have an associated schema.

To Reproduce

To reproduce the bug, you can use the following sample code:

import daft

if __name__ == "__main__":
    df = daft.from_pylist(
        [
            {
                "typeName": "Table",
                "attributes": {
                    "qualifiedName": "default.table1",
                    "name": "table1",
                    "owner": "Alice",
                }
            }
        ]
    )
    print(daft.get_version())
    df.show()
    df.select("typeName", "attributes.*").show()

This code creates a Daft DataFrame from a Python list, prints the Daft version, displays the DataFrame, and then attempts to select all columns from the attributes struct using the attributes.* syntax. However, this results in an exception being raised.

Expected Behavior

The expected behavior is that the wildcard select on the struct should work as expected, and the code should run without any errors. The attributes.* syntax should select all columns from the attributes struct, and the resulting DataFrame should contain the selected columns.

Component(s)

The component affected by this bug is the Expressions module in Daft.

Additional Context

No additional context is provided for this bug.

Workaround

Unfortunately, there is no known workaround for this bug. The issue is specific to the latest version of Daft (0.4.7), and the only solution is to downgrade to a previous version, such as 0.3.15, where the wildcard select on a struct works as expected.

Conclusion

In conclusion, the wildcard select on a struct does not work in the latest version of Daft (0.4.7). This issue is specific to the Expressions module and results in an exception being raised when trying to select all columns from a struct using the attributes.* syntax. While there is no known workaround for this bug, downgrading to a previous version of Daft, such as 0.3.15, can resolve the issue.

Future Development

To resolve this issue, the Daft development team should investigate the cause of the problem and provide a fix in a future release. This may involve updating the Expressions module to correctly handle wildcard selects on structs.

Recommendations

Based on this issue, we recommend the following:

Downgrade to a previous version of Daft, such as 0.3.15, if you need to use the wildcard select on a struct.
Monitor the Daft development team's progress on resolving this issue.
Provide feedback to the Daft development team on this issue to help prioritize its resolution.

Daft Version Compatibility

The following Daft versions are affected by this issue:

0.4.7: The latest version of Daft, where the wildcard select on a struct does not work.
0.3.15: A previous version of Daft, where the wildcard select on a struct works as expected.

Daft Documentation

For more information on Daft, including its documentation and release notes, please visit the Daft website.

Daft Community

Q: What is the issue with wildcard select on a struct in Daft?

A: The issue is that the wildcard select on a struct does not work in the latest version of Daft (0.4.7). When trying to select all columns from a struct using the attributes.* syntax, an exception is raised.

Q: What is the expected behavior of wildcard select on a struct?

A: The expected behavior is that the wildcard select on a struct should work as expected, and the code should run without any errors. The attributes.* syntax should select all columns from the attributes struct, and the resulting DataFrame should contain the selected columns.

Q: What is the workaround for this issue?

A: Unfortunately, there is no known workaround for this bug. The issue is specific to the latest version of Daft (0.4.7), and the only solution is to downgrade to a previous version, such as 0.3.15, where the wildcard select on a struct works as expected.

Q: Why is this issue specific to the latest version of Daft?

A: The issue is specific to the latest version of Daft (0.4.7) because of changes made to the Expressions module. The changes introduced a bug that affects the wildcard select on a struct.

Q: How can I report this issue to the Daft development team?

A: You can report this issue to the Daft development team by creating a new issue on the Daft GitHub page. Please provide as much detail as possible, including the code that reproduces the issue and any relevant error messages.

Q: What is the status of the issue being fixed?

A: The Daft development team is aware of the issue and is working on a fix. However, no timeline has been provided for when the fix will be released.

Q: Can I use a different library instead of Daft?

A: Yes, there are other libraries available that provide similar functionality to Daft. Some popular alternatives include Pandas and NumPy.

Q: How can I stay up-to-date with the latest developments on this issue?

A: You can stay up-to-date with the latest developments on this issue by following the Daft GitHub page and the Daft mailing list. You can also check the Daft documentation and release notes for any updates on the issue.

Q: Can I contribute to the fix of this issue?

A: Yes, you can contribute to the fix of this issue by creating a pull request on the Daft GitHub page. Please make sure to follow the Daft contribution guidelines and provide a clear and concise description of the changes you are making.

Q: What is the impact of this issue on my project?

A: The impact of this issue on your project will depend on how you are using Daft and whether you are affected by the wildcard select on a struct. If you are using Daft extensively in your project, you may need to consider downgrading to a previous version or using a different library.

Q: Can I get help from the Daft community on this issue?

A: Yes, you can get help from the Daft community on this issue by posting on the Daft mailing list or asking for help on the Daft GitHub page. The Daft community is active and helpful, and many users have already reported similar issues and provided solutions.