- Errors while loading of invalid data become correctly handled.
- Fixed a bug that cache is broken. [GitHub#25] [Reported by KITAITI Makoto]
- KITAITI Makoto
- Updated for the latest Droonga Engine 1.1.0.
- Supports uber-cache 2.0.0.
- New endpoints are introduced to inspect connections to Droonga Engine nodes.
/engines
returns the list of currently conencted Droonga Engine nodes./connections
returns detailed status of internal connections to Droonga Engine nodes.
- Always reconnects to Droonga Engine nodes when there is any change around the Droonga cluster.
- Query parameters for
/droonga/*
endpoints are used as the message body.
- Connects to active engine nodes of the cluster of the associated engine node correctly. Previous version unexpectedly kept connections to already unjoined engine nodes.
- Supports multiple Droonga Engine nodes as its backends. Now express-droonga can work like a load balancer.
- The list of connecting Droonga Engine nodes can be automatically updated
based on the actual list of active members in the cluster.
This feature is activated by the
syncHostNames
option for theapplication.droonga()
method.
- Debug logs are now reported via given logger.
- Return cached responses correctly.
- Supports paths like
/droonga/(command name)
withGET
method. - Supports paths like
/droonga/(command namespace)/(command name)
withGET
andPOST
method. - Works with the Express 4.4.4.
- Groonga compatible
load
command withGET
method is available. - Query parameter
group_by[(column name)][attributes]
for the RESTsearch
command now accepts simple comma-separeted string value.
- Works with the Express 4.0.
- Keeps the process alive even if it is disconnected from the Droonga Engine.
- Groonga compatible
load
command withPOST
method is available. (Note:load
command withGET
method is not supported yet.)
- The bundled HTTP server application is removed. Instead, use another project droonga-http-server.
- Parallel connections from the Droonga Engine are established correctly.
- A middleware for response caches is available now.
You can see the statistics via
/cache/statistics
. - Query parameters
attributes
,group_by
, andadjusters
are available for a RESTsearch
command (via/tables/:tableName
).
The first major release! No changes since 0.9.9.
- search: Improved query name in
queries
parameter. It was alwaysresult
. Now, it is guessed from table name parameter.
- Supported HTTP streaming.
A bug fix release of 0.8.1.
The first release!