oceandb-elasticsearch-driver 0.4.4

🐳 OceanDB ElasticSearch Driver (Python).

oceandb-elasticsearch-driver

🐳 Elasticsearch driver for OceanDB (Python). oceanprotocol.com

---

Table of Contents

• Features
• Prerequisites
• Quickstart
• Environment variables
• Queries

---

Features

Elasticsearch driver to connect implementing OceanDB.

Prerequisites

You should have running a elasticsearch instance.

Quickstart

First of all we have to specify where is allocated our config. To do that we have to pass the following argument:

--config=/path/of/my/config

If you do not provide a configuration path, by default the config is expected in the config folder.

In the configuration we are going to specify the following parameters to

    [oceandb]

    enabled=true            # In order to enable or not the plugin
    module=elasticsearch    # You can use one the plugins already created. Currently we have elasticsearch, mongodb and bigchaindb.
    module.path=            # You can specify the location of your custom plugin.
    db.hostname=localhost   # Address of your Elasticsearch instance.
    db.port=9200            # Port of your Elasticsearch rest API.
    db.username=elastic     # If you are using authentication, elasticsearch username.
    db.password=changeme    # If you are using authentication, elasticsearch password.
    db.index=oceandb        # Elasticsearch index name

Once you have defined this the only thing that you have to do it is use it:

    oceandb = OceanDb(conf)
    oceandb.write({"value": "test"}, id)

Environment variables

When you want to instantiate an Oceandb plugin you can provide the next environment variables:

• $CONFIG_PATH
• $MODULE
• $DB_HOSTNAME
• $DB_PORT
• $DB_INDEX
• $DB_USERNAME
• $DB_PASSWORD

Queries

You can query the DDO using predefined fields or provide the path to the desired fields yourself.

All queries use a common format:

{
  "query": {
    "field": ["value1", "value2"]
  }
}

Querying predefined fields

Predefined fields include:

• cost

  Could receive one or two parameters. If you only pass one assumes that your query is going to start from 0 to your value.

  Next query: query:{"cost":[0,10]}

  It is transformed to: {"service.attributes.main.cost":{"$gt": 0, "$lt": 10}}

• license

  It is going to retrieve all the documents with license that you are passing in the parameters, if you do not pass any value retrieve all.

  {"license":["Public domain", "CC-YB"]}

• type

  It is going to check that the following service types are included in the ddo.

  {"type":["Access", "Metadata"]}

• sample

  Check that the metadata include a sample that contains a link of type sample. Do not take parameters.

  {"sample":[]}

• categories

  Retrieve all the values that contain one of the specifies categories.

  {"categories":["weather", "meteorology"]}

• created

  Retrieve all the values that has been created between two dates.

  {"created":['2016-02-07T16:02:20Z', '2016-02-09T16:02:20Z']}

• dateCreated

  Retrieve all the values that has been created between two dates.

  {"dateCreated":['2016-02-07T16:02:20Z', '2016-02-09T16:02:20Z']}

• datePublished

  Retrieve all the values that has been published between two dates.

  {"datePublished":['2016-02-07T16:02:20Z', '2016-02-09T16:02:20Z']}

• updatedFrequency

  Retrieve all the values that contain one of the specifies updated frecuencies.

  {"updatedFrequency":["monthly"]}

• text Retrieve all the values that match with the text sent.

  {"text":["weather"]}

Querying custom fields as texts

You can also query the DDO by value of any field. To do that, you will need to provide the full path inside the metadata instead of just the field name.

For example:

{
  "query": {
    "service.attributes.additionalInformation.customField": ["customValue1", "customValue2"]
  }
}

Querying custom fields as intervals

To do that, you will need to provide the full path inside the metadata instead of just the field name, and values as integers or floats

For example:

{
  "query": {
    "service.attributes.additionalInformation.customNumber": [3, 6]
  }
}

which is translated to:

{
    "bool": 
    {
        "must": [
            {"bool":
                {"should": [
                    {"range": {"service.attributes.additionalInformation.customNumber": {"gte": 3, "lte": 6}}}
                ]
                }
            }
        ]
    }
}

Code style

The information about code style in python is documented in this two links python-developer-guide and python-style-guide.

Testing

Automatic tests are setup via Travis, executing tox. Our test use pytest framework.

New Version

The bumpversion.sh script helps to bump the project version. You can execute the script using as first argument {major|minor|patch} to bump accordingly the version.

License

Copyright 2018 Ocean Protocol Foundation Ltd.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.