Farrukh - It looks like you have been building Solr (based on seeing Calcite 1.32 in the logs which was only recently updated) - can you try out https://github.com/apache/solr/pull/1044 with security manager enabled to see if that fixes the issue you ran into?
Kevin Risden On Sun, Sep 25, 2022 at 11:08 AM Kevin Risden <kris...@apache.org> wrote: > So the stack trace lines up with > https://github.com/apache/calcite/blob/main/core/src/main/java/org/apache/calcite/config/CalciteSystemProperty.java#L189 > > It looks like Calcite / Solr SQL doesn't like the Java security manager > being enabled; there is an exception checking those paths. > > A workaround is to set SOLR_SECURITY_MANAGER_ENABLED=false which will > disable the security manager in Java and should allow this to work. This > was only changed to true in Solr 9.0. > > Filed https://issues.apache.org/jira/browse/SOLR-16433 > > Kevin Risden > > > On Sat, Sep 24, 2022 at 2:23 PM Farrukh Zamir <farrukhza...@gmail.com> > wrote: > >> >> On Sat, 24 Sep 2022, 20:17 Farrukh Zamir, <farrukhza...@gmail.com> wrote: >> >>> Following are the links to images of my error mentioned in previous >>> mail. Sequence wise. >>> >>> >>> https://drive.google.com/file/d/16Z-nQHhvzXVQ2oSyfqsdCSZTofLDcuZ9/view?usp=drivesdk >>> >>> >>> https://drive.google.com/file/d/1oIMKI_3cdUwCiZ-86XLH8VfQXB9URqwn/view?usp=drivesdk >>> >>> >>> https://drive.google.com/file/d/1AL-DFI0qlVjnDa_bJIUsp-m_s52CHzlL/view?usp=drivesdk >>> On Sat, 24 Sep 2022, 14:16 Farrukh Zamir, <farrukhza...@gmail.com> >>> wrote: >>> >>>> Hi, >>>> i have installed solr 9.0.0 on my server on windows. It installed >>>> successfully. Cloud mode required for sql was also configured >>>> successfully./sql handle is also being shown in plugins in core. >>>> [image: image.png] >>>> But when i execute sql query. Following error shows. i have said the >>>> library path and copied jar which were required done every thing but this >>>> error does not goes. >>>> >>>> [image: image.png] >>>> Please help me in this regard. what i am doing wrong. >>>> >>>
