Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Broken Backwards compatibility around bytes_view #14983

Closed
david-engelmann opened this issue Dec 15, 2022 · 6 comments
Closed

Broken Backwards compatibility around bytes_view #14983

david-engelmann opened this issue Dec 15, 2022 · 6 comments

Comments

@david-engelmann
Copy link

Describe the bug, including details regarding any error messages, version, and platform.

Here is the full command that failed with all the included directories

/opt/conda/envs/turbodbc-dev/bin/x86_64-conda-linux-gnu-c++ -Dturbodbc_arrow_support_EXPORTS -I/src/cpp/turbodbc_arrow/Library -I/src/cpp/turbodbc_arrow/../cpp_odbc/Library -I/src/cpp/turbodbc_arrow/../turbodbc/Library -isystem /opt/conda/envs/turbodbc-dev/include/python3.8 -isystem /opt/conda/envs/turbodbc-dev/lib/python3.8/site-packages/numpy/core/include -isystem /opt/conda/envs/turbodbc-dev/lib/python3.8/site-packages/pyarrow/include -isystem /src/pybind11/include -fvisibility-inlines-hidden -fmessage-length=0 -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem /opt/conda/envs/turbodbc-dev/include -Wall -Wextra -g -O0 -pedantic -fprofile-arcs -ftest-coverage -fPIC -fvisibility=hidden   -std=c++11 -MD -MT cpp/turbodbc_arrow/Library/CMakeFiles/turbodbc_arrow_support.dir/src/python_bindings.cpp.o -MF cpp/turbodbc_arrow/Library/CMakeFiles/turbodbc_arrow_support.dir/src/python_bindings.cpp.o.d -o cpp/turbodbc_arrow/Library/CMakeFiles/turbodbc_arrow_support.dir/src/python_bindings.cpp.o -c /src/cpp/turbodbc_arrow/Library/src/python_bindings.cpp
/opt/conda/envs/turbodbc-dev/include/arrow/util/bytes_view.h:26:25: error: 'basic_string_view' in namespace 'std' does not name a template type
using bytes_view = std::basic_string_view<uint8_t>;

It also states that this is only defined for C++17 and on. Currently, the turbodbc build with pyarrow10 version is failing because of this. The default build behavior of turbodbc uses the following commands add_definitions("-std=c++11") and extra_compile_args.append("--std=c++11")

I believe this is the final blocker for bumping turbodbc requirements to greater than 9.

Component(s)

Python

@raulcd
Copy link
Member

raulcd commented Dec 15, 2022

Arrow 10.0.0 bumped to C++ 17, see: #13991
I think turbodbc will have to upgrade accordingly.

@david-engelmann
Copy link
Author

I'm testing with C++17 now, the build is successful, test are currently running

@raulcd
Copy link
Member

raulcd commented Dec 15, 2022

Also, in case you are interested I sent this email today to the dev mailing list around removing some integration tests around turbodbc because they have been commented for 8 months now: https://lists.apache.org/thread/nqbbrnsdf86j0lj4j1rhbyxgs5o33p5w
Just sharing in case you want to answer as I haven't seen many other people working on turbodbc lately.

@david-engelmann
Copy link
Author

Are you removing Arrow test around turbodbc nightly, or Turbodbc test around Arrow Nightly. The Turbodbc test around Arrow Nightly should working going forward. I was able to confirm bumping to C++17 was the only remaining issue

@raulcd
Copy link
Member

raulcd commented Dec 15, 2022

There are two nightly jobs that have been commented for 8 months and would be cleaned up:

  • Arrow master with turbodbc master
  • Arrow master with latest tag of turbodbc (right now 4.5.5)

@david-engelmann
Copy link
Author

I see no reason why Arrow would need to keep those test, specially if they've been commented out for 8 months with no issue. Turbodbc will keep the test with arrow nightly. I'm going to close this issue out because the bump to c++17 resolved the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants