Apache Solr with DBine
How to connect DBine to Apache Solr and what you can do once it's connected. This page is written from what the Apache Solr driver says about itself, so it matches the version of DBine you download.
Connect
- In DBine, open New connection.
- Pick Apache Solr in the list of engines.
- Fill in the fields below, press Test connection and then Save.
Default port: 8983.
General
| Field | Description |
|---|---|
| Server required | Server name or full URL. If the URL has no port, the one in the Port field is used. Example: localhost or https://my-solr:8983 |
| Port | Default: 8983 |
| User | |
| Password | Kept in the system keychain, never in DBine's files. |
| Read-only | On or off. |
SSH tunnel. The connection can go through an SSH server, even through a chain of bastions, with a password, a private key or the SSH agent. The server's fingerprint is checked against known_hosts or confirmed the first time.
SSL/TLS
| Field | Description |
|---|---|
| Encrypt the connection (TLS) | On or off. |
| Trust the server certificate | On or off. |
What the explorer shows
The objects appear right under the connection:
- Collections
Query editor
The editor uses Apache Solr's own query syntax, in JSON, with completion for the connection's objects. Statements and commands run against the database selected in the tab.
What the editor accepts:
Console syntax: one request per block, `METHOD /path` and an optional JSON body; blocks are separated by a blank line. The /solr prefix can be omitted.
GET /solr/<collection>/select?q=*:*&rows=10
POST /solr/<collection>/update?commit=true + [ {"id": "1", …} ]
POST /solr/<collection>/schema + {"add-field": {"name": "x", "type": "string"}}
SELECT … FROM <collection> (Solr SQL, SolrCloud only)
DBine extensions (they work the same on standalone and SolrCloud):
PUT /solr/<name> + {"configSet": "_default", "numShards": 1, "replicationFactor": 1} (optional body)
creates a core (standalone, CoreAdmin CREATE) or a collection (SolrCloud, Collections API CREATE).
With ?if_not_exists=true it does nothing if it already exists.
DELETE /solr/<name>
deletes the core with its data (UNLOAD) or the collection (DELETE). With ?if_exists=true it does not fail if it does not exist.Ready-made templates for new objects:
- New collection (script)
- New field
- New dynamic field
- New field copy (copyField)
- New field type
Tools for Apache Solr
Available
- Graphical execution plans
- Server monitor
- Visual designer for new objects
- Rename objects
- Compare and sync schemas
- Native bulk load when migrating data
- Users and permissions
- Backups
Not available for Apache Solr
- Live query profiler
- Sessions and running queries
- End a session
- Locks: who blocks whom
- Cancel another session's query from the sessions list
- Manual transactions (commit and rollback)
- Index usage
- Create databases
- Drop databases
- Database properties
- Relations in the ER diagram
- Clone tables
Why a tool doesn't apply to an engine, and the details of each one, are in the engine support reference.
Generated from the Apache Solr driver 0.1.10, which DBine downloads the first time you connect to Apache Solr.