xumingming closed issue #5044: [VL] spark.read.csv("/tmp/test.csv") throws
Exception
URL: https://github.com/apache/incubator-gluten/issues/5044
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
xumingming commented on issue #5044:
URL:
https://github.com/apache/incubator-gluten/issues/5044#issuecomment-2024637533
@PHILO-HE Thanks for the information, closing it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
PHILO-HE commented on issue #5044:
URL:
https://github.com/apache/incubator-gluten/issues/5044#issuecomment-2022823432
> @PHILO-HE Thanks for the information! I tried with parquet data(nation
table in TPCH), the details are the following:
>
> ```
> == Fallback Summary ==
> (4)
xumingming commented on issue #5044:
URL:
https://github.com/apache/incubator-gluten/issues/5044#issuecomment-2020579428
@PHILO-HE Thanks for the information! I tried with parquet data(nation table
in TPCH), the details are the following:
```
== Fallback Summary ==
(4)
PHILO-HE commented on issue #5044:
URL:
https://github.com/apache/incubator-gluten/issues/5044#issuecomment-2019393809
Hi @xumingming, the exception looks irrelevant. Currently, Gluten doesn't
support CSV format. So reading CSV will fall back to vanilla Spark. You can
check the fallback
xumingming commented on issue #5044:
URL:
https://github.com/apache/incubator-gluten/issues/5044#issuecomment-2014638253
Full log:
```
scala> val path = "/tmp/person.csv"
path: String = /tmp/person.csv
scala> val person = spark.read.csv(path);
E20240322
xumingming commented on issue #5044:
URL:
https://github.com/apache/incubator-gluten/issues/5044#issuecomment-2014061708
@zhztheplayer The result is correct, just a simple select.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
zhztheplayer commented on issue #5044:
URL:
https://github.com/apache/incubator-gluten/issues/5044#issuecomment-2011655932
Was the query result correct?
Sometimes this log doesn't mean there is anything wrong. If it's the case we
can find a way to suppress that log from Velox.
--
