Would it be possible to extract Skyhook from Arrow's build system?
Short of that, maybe just moving the Skyhook sub-tree (and related
files outside of it) into its own repo would be a start, even if it
doesn't build and we just documented that fact. i.e., make it a
source-only archive.

On Mon, May 5, 2025 at 12:09 PM Aldrin <octalene....@pm.me.invalid> wrote:
>
> > move it into a standalone or contrib repo
>
> I would be willing to do this, but I can only imagine an approach that 
> essentially looks like a repo that has the relevant code but is frozen on 
> some snapshot of Arrow (or whatever version someone is willing to rebase 
> onto, for as long as they're willing to rebase it).
>
> Is there a way to do this that doesn't essentially look like [1]?
>
> [1]: https://github.com/uccross/skyhookdm-arrow
>
>
> -Aldrin
>
>
> On Mon, May 5, 2025 at 10:57, Bryce Mecum <bryceme...@gmail.com> wrote:
>
> +1 for deprecating. I think it would be great if we could find a
> volunteer to move it into a standalone or contrib repo so it's easy to
> find rather than removing it from the source tree.
>
> On Mon, May 5, 2025 at 1:05 AM Antoine Pitrou <anto...@python.org> wrote:
> >
> >
> > Hello,
> >
> > "Skyhook" is a little-known C++ component that interfaces Arrow with the
> > Ceph distributed filesystem. It received it last non-trivial change in 2022:
> > https://github.com/apache/arrow/commit/546c3771a209cbcac5e03cf26e07bcd8c9601d5a
> >
> > You won't find much documentation for it except for an example and some
> > API docs:
> > https://arrow.apache.org/docs/search.html?q=skyhook
> >
> > Most Google search results point to the 2022 paper that presents the
> > original work:
> > https://www.google.com/search?q=%22arrow%22+%22skyhook%22
> >
> > A C++ code search only brings Arrow C++ itself (there are unrelated C++
> > projects that use the word "skyhook"):
> > https://grep.app/search?f.lang.pattern=c%2B%2B&words=true&q=skyhook
> >
> > Should we deprecate the Skyhook component and remove it in a release or two?
> >
> > Regards
> >
> > Antoine.
> >

Reply via email to