As others have said, the next step is to create a jira case. Please do that. Otherwise parts of this discussion will be forgotten or not acted upon.
I agree with Michael’s observation. A lot of javadoc, tests, and user doc will be needed to get this to project standards. Did you, or would you, consider making this functionslity part of the file/web adapter? We have talked about this for a long time. There is a continuum from getting data from the file system (simple), getting it from HTTP (more complex), to taking up APIs (most complex). And dealing with the format of the data that comes back (csv, xml, json) is orthogonal to the protocol you used to get it. If we don’t correctly factor those concerns our users will be pissed off that adapters handle csv data differently depending how we got it. Julian > On Nov 13, 2025, at 07:29, Michael Mior <[email protected]> wrote: > > Oleg, > > This looks very promising! I would suggest you open up a JIRA case to track > what would need to be done to contribute this adapter. Two things that > stick out to me is that there don't appear to be any tests or Javadoc in > the repository. This is perfectly reasonable as a starting point of course, > but maintenance by the community is going to be much easier with proper > tests and documentation. > > Aside from that, I think there are a lot of interesting things that could > be done with the adapter in the future (not as prerequisites for > contributing the adapter). For one, alternative authentication methods > would likely be helpful. For REST APIs that don't support disjunction, it > seems like you may be able to configure the optimizer such that multiple > requests would be issued (although this leaves the challenge of > deduplication for results that match multiple conditions). As you > mentioned, I think OpenAPI support would be very interesting given how > popular the format is. > > -- > Michael Mior > [email protected] > > >> On Tue, Nov 11, 2025 at 4:13 AM Oleg Alekseev <[email protected]> >> wrote: >> >> >> >> >> Hello Apache Calcite community, >> >> My name is Oleg Alekseev, and I have developed a new adapter called >> CalciteRestAPIAdapter designed to retrieve data from REST services using >> standard SQL syntax. This adapter leverages the Apache Calcite framework, >> enabling access to REST APIs through JDBC by configuring service schemas >> and tables via XML files. >> >> The adapter is publicly available on GitHub: >> https://github.com/oalekseev/CalciteRestAPIAdapter >> >> I would like to propose this adapter as a contribution to the Apache >> Calcite project to make it accessible and beneficial to the wider community. >> >> Please let me know the appropriate process and any guidelines I should >> follow to move forward with submitting this contribution. >> >> Thank you for your time and consideration. >> >> Best regards, >> Oleg Alekseev >> >>
