-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot store a dashboad when using a remote server #295
Comments
hi @mosuka, First of all thank you for the fast reply! So, it is not a bug, it is a feature? Why dashboards should be stored in a "remote" instance? Thanks! |
Banana (localhost:8111) visualizes the data of connected Solr (localhost:8008). Also, it stores dashboard settings to the same Solr (localhost:8008). |
So, could you guys please confirm, that storing Banana dashboards in a dedicated solr instance is not supported by design? UPDATE: |
fantastic! thanks a lot! |
@jetnet @aadel @mosuka I added the feature to save / load dashboards from another Solr server in the latest commit to |
hi guys!
I'd like to have a dedicated small solr instance for Banana (v1.6.11) only (localhost:8111) and a working Solr instance with data (localhost:8008):
config.js
and the config of a dashboard:
Solr Server / Fusion Query Pipeline:
http://localhost:8008/solr/
Collection Name:
project
The UI (http://localhost:8111/solr/banana/index.html) can connect and visualize data from the "remote" instance (port:8008), but when I try to save the dashboad, it uses the remote instance (port:8008 not the "local" one - 8111) to store the dashboard:
http://localhost:8008/solr/banana/update?commit=true
Obviously, the request returns 404 - "not found", because the "banana" index exist in the "local" instance only.
Question: why Banana does use the "Solr Server" URL from the dashboard's settings and not the "main" one from the "config.js" to store its own data?
Thank you!
The text was updated successfully, but these errors were encountered: