Age | Commit message (Collapse) | Author |
|
* I can't swear on this, but it seems the presence of these statements
was causing elasticsearch to act weird.
|
|
|
|
* Update the indexes mappings to be compatible with the newer
Elasticsearch 6.2.* series.
Close the index before updating it, and reopen it after to help with
the re-indexing of the data.
* Update the error logger to include the exception that was thrown.
|
|
|
|
* Prevent elasticsearch from analysing and tokenising the email_address
field so as to avoid issue with getting back all email addresses with
the same domain as the one being searched for.
|
|
testing
|
|
|
|
testing
* Fix conflicts
|
|
|
|
PYTHONPATH needed as
it is now in the Guix build.
|
|
* Update functions to make them more testable.
* Update code using updated functions.
|
|
* Instead of checking for the state of elasticsearch at startup, check
the state at the moment the user requests a feature that depends on
elasticsearch.
This reduces the chances that the user is dropped onto an exception
page when elasticsearch server goes down.
|
|
* Add some extra checks to ensure that elasticsearch is running before
presenting the UI to the user.
|
|
* Refactor code that can be used in more than one place to a more
generic method/function that's called by other methods
|
|
* If elasticsearch server is down, or the configuration variables are
not provided at startup or in a configuration file, then do not allow
the system to simply crash, but instead, inform the user that they
cannot use the services that depend on elasticsearch to be running.
|
|
* Elasticsearch need a short delay after adding document for it to index
the document for subsequent access.
|
|
* On successful login via OAuth2, save the details of the user in
elasticsearch store, to avoid hitting the external provider for the
basic details.
|
|
* Collect variables and functions for using the elasticsearch system in
a separate module.
|
|
PYTHONPATH needed as
it is now in the Guix build.
|
|
* Update functions to make them more testable.
* Update code using updated functions.
|
|
* Instead of checking for the state of elasticsearch at startup, check
the state at the moment the user requests a feature that depends on
elasticsearch.
This reduces the chances that the user is dropped onto an exception
page when elasticsearch server goes down.
|
|
* Add some extra checks to ensure that elasticsearch is running before
presenting the UI to the user.
|
|
* Refactor code that can be used in more than one place to a more
generic method/function that's called by other methods
|
|
* If elasticsearch server is down, or the configuration variables are
not provided at startup or in a configuration file, then do not allow
the system to simply crash, but instead, inform the user that they
cannot use the services that depend on elasticsearch to be running.
|
|
* Elasticsearch need a short delay after adding document for it to index
the document for subsequent access.
|
|
* On successful login via OAuth2, save the details of the user in
elasticsearch store, to avoid hitting the external provider for the
basic details.
|
|
* Collect variables and functions for using the elasticsearch system in
a separate module.
|