m-g-r commented on PR #2538:
URL: https://github.com/apache/thrift/pull/2538#issuecomment-1224319945

   Hi, I currently just continue to use it. And the Common Lisp language 
backend seems to be quite complete, stable and generates efficient code. I use 
it to talk to Accumulo via the Accumulo Proxy and that allows for high 
ingestion rates as I have described in this article "Almost 600,000 entries per 
second from Lisp to Accumulo" at 
https://observablehq.com/@m-g-r/almost-600000-entries-per-second-from-lisp-to-accumulo
 As written in section "Comparison", it seems safe to argue that in this test 
we achieve a comparable raw ingestion performance to similar measurements of 
the ingestion rate to Apache Accumulo.
   
   I was basically frankly surprised that you just remove such a complete 
language backend given that seems this seems to be the very thing Apache Thrift 
is about: a "language-independent software stack" allowing "programs written in 
different programming languages" to communicate with each other.
   
   Admittingly, I just use James' `de.setf.thrift` at 
https://github.com/lisp/de.setf.thrift directly and have just thrift via the 
Ubuntu package thrift-compiler installed to generate the lisp code from the 
thrift definition file...
   
   Hm, THRIFT-5410 “CL build broken: Component :NET.DIDIERVERNA.CLON.TERMIO not 
found” is according to your email 
https://www.mail-archive.com/[email protected]/msg50775.html just a test 
not running, right? In file "thrift/src/test/cl/make-test-server.lisp" and that 
breaks your build system, or rather the continuous integration service? That 
test uses Didier's `clon` to parse commond-line options in a standalone 
application `TestClient`.
   
   Let me see if I can reproduce that. Currently looking at make running to 
build thrift which seems to take a while.
   
   Cheers, Max


-- 
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 specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to