Currently, aggregation APIs (groupby, reductions, rolling, etc.) are scattered around in multiple files and there are inconsistencies between the directory structures in cpp/include/, cpp/src/, cpp/tests/, and cpp/benchmarks/. For example:
cpp/include/:
cpp/src/:
I'd like to be able to call LCASE on a string column to convert it to lowercase, like in MySQL. This is an alias for LOWER, which is noted in #1135 . This is listed as a supported operation on string columns in the Calcite reference, but it may need not currently be available without some changes based on the following:
from pyspark.sql import SparkSession
from blazingsql import Bla
Our dask update graphs are not properly optimized.
We ussually use dask.dataframe optimization and set ave_width=repartition_ratio for kartothek.io.dask.dataframe.update_dataset_from_ddf graphs. We should return an optimized graph from update_dataset_from_ddf to make our users' life simple.
We already have code that does this, whoever picks this up can ping me
It would be helpful to have Fletchgen output warnings for unused metadata fields that start with fletcher_. For example, (this happened to me) when someone adds fletchgen_epc to Schema metadata instead of Field metadata.
Add a description, image, and links to the arrow topic page so that developers can more easily learn about it.
To associate your repository with the arrow topic, visit your repo's landing page and select "manage topics."
I think it would be nice if there was a reversed version of humanize, i.e. a function that parses human readable input like "20 hours ago" and produces an Arrow object than can be used in scripts with ease.