Since you say, "I already started with Zoekt", I'm guessing you are facing some problem large enough to cause you to abandon your work so far.
I say this because to "rewrite it in solr" means, among other things, rewriting all your Go code in Java, since Zoekt is in Go and Solr is in Java. I am guessing that instead, your best bet is to ask within the Zoekt community how to resolve the problem you are facing that's motivating you to switch. If, after that, you still want to switch, then before you switch, you should recreate the same scenario using Solr, and ask here *a specific question about how to use Solr* to address the issue. Only very rarely is the best approach to a problem to re-implement everything you've done so far in another language / another codebase. Said differently, if you cannot resolve your issues using Zoekt, it's doubtful they can be resolved with Solr. Whatever challenges you are facing working with the Zoekt code are likely to be the same challenges working with the Solr code. What you are attempting is challenging, plain and simple. Andrew Witt Senior Software Engineer II Learning A-Z, a Cambium Learning® Group Company andrew.w...@learninga-z.com -----Original Message----- From: anon anon <anonimoussech...@gmail.com> Sent: Wednesday, March 19, 2025 7:33 PM To: users@solr.apache.org Subject: index source code with solr combined with a SAST for cyber security purpose Hello, I wanted to combine the power of a search engine with a SAST. I already started with Zoekt. I want to know if I should fork zoekt or solr. I am wondering: - If I can rewrite it in solr for more maintainability - if I SHOULD actually maintain zoekt instead of solar in order to not have to reinvent the whell (exactly like solr) - AND THE MOST IMPORTANT: would it be easier to implement, maintain and use the SAST from zoekt code base instead of solr? Maybe could I transfer the SAST part to another program and the zoekt search from zoekt software only? Whatis the best deal for the open source community please? Best regards.
