Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[FEA] support spark.sql.legacy.timeParserPolicy when parsing CSV files #1111

Closed
andygrove opened this issue Nov 13, 2020 · 1 comment · Fixed by #4853
Closed

[FEA] support spark.sql.legacy.timeParserPolicy when parsing CSV files #1111

andygrove opened this issue Nov 13, 2020 · 1 comment · Fixed by #4853
Assignees
Labels
feature request New feature or request

Comments

@andygrove
Copy link
Contributor

Is your feature request related to a problem? Please describe.
We should support spark.sql.legacy.timeParserPolicy when parsing CSV files

@andygrove andygrove added feature request New feature or request ? - Needs Triage Need team to review and classify labels Nov 13, 2020
@andygrove andygrove added this to the Nov 9 - Nov 20 milestone Nov 13, 2020
@andygrove andygrove self-assigned this Nov 13, 2020
@andygrove andygrove removed this from the Nov 9 - Nov 20 milestone Nov 19, 2020
@sameerz sameerz removed the ? - Needs Triage Need team to review and classify label Nov 24, 2020
@sameerz
Copy link
Collaborator

sameerz commented Nov 24, 2020

Needs additional support for CSV parsing in cudf.

@andygrove andygrove removed their assignment Dec 14, 2020
@revans2 revans2 mentioned this issue Apr 1, 2021
38 tasks
@andygrove andygrove self-assigned this Feb 16, 2022
@andygrove andygrove added this to the Feb 14 - Feb 25 milestone Feb 16, 2022
tgravescs pushed a commit to tgravescs/spark-rapids that referenced this issue Nov 30, 2023
…IDIA#1111)

Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
feature request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants