Version 1.0.0

.gitignore

@@ -30,3 +30,6 @@ exdgraph-*.tar
 
 # Data directory when running Dgraph from docker-compose for test purposes
 /dgraph_data
+
+# TLS folder with certificates for testing
+/tls/*

.travis.yml

@@ -1,8 +1,9 @@
 language: elixir
 
 elixir:
-  - 1.6
+  - 1.7
   - 1.8
+  - 1.9
 
 otp_release:
   - 20.0
@@ -11,6 +12,9 @@ matrix:
   include:
     - elixir: 1.8
       otp_release: 21.2
+    - elixir: 1.9
+      otp_release:
+      otp_release: 22.0
 
 cache:
   directories:

Changelog.md

@@ -6,6 +6,8 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unreleased]
 
+- Remove retry since DBConnection 2 implements a retry mechanism.
+
 ## [0.2.0-beta.3] - 2019-07-31
 
 - Test against Dgraph `v1.0.16`

README.md

@@ -2,7 +2,7 @@
 
 **ExDgraph is functional but I would be careful using it in production. If you want to help, please drop me a message. Any help is greatly appreciated!**
 
-ExDgraph is a gRPC based client for the [Dgraph](https://github.com/dgraph-io/dgraph) database. It uses the [DBConnection](https://hexdocs.pm/db_connection/DBConnection.html) behaviour to support transactions and connection pooling via [Poolboy](https://github.com/devinus/poolboy). Works with Dgraph v1.0.16 (latest).
+ExDgraph is a gRPC based client for the [Dgraph](https://github.com/dgraph-io/dgraph) database. It uses [DBConnection](https://hexdocs.pm/db_connection/DBConnection.html) to support transactions and connection pooling. Works with Dgraph v1.0.16 (latest).
 
 > Dgraph is an open source, horizontally scalable and distributed graph database, providing ACID transactions, consistent replication and linearizable reads. [...] Dgraph's goal is to provide Google production level scale and throughput, with low enough latency to be serving real time user queries, over terabytes of structured data. ([Source](https://github.com/dgraph-io/dgraph))
 
@@ -62,8 +62,7 @@ Add the configuration to your respective configuration file:
 config :ex_dgraph, ExDgraph,
   hostname: 'localhost',
   port: 9080,
-  pool_size: 5,
-  max_overflow: 1
+  pool_size: 5
 ```
 
 And finally don't forget to add ExDgraph to the supervisor tree of your app:
@@ -299,7 +298,7 @@ request = ExDgraph.Api.Request.new(query: query)
 {:ok, msg} = channel |> ExDgraph.Api.Dgraph.Stub.query(request)
 
 # Parse result
-json = Poison.decode!(msg.json)
+json = Jason.decode!(msg.json)
 ```
 
 ## Using SSL
@@ -311,7 +310,6 @@ config :ex_dgraph, ExDgraph,
   # default port considered to be: 9080
   hostname: 'localhost',
   pool_size: 5,
-  max_overflow: 1,
   ssl: true,
   cacertfile: '/path/to/MyRootCA.pem'
 ```
@@ -332,7 +330,6 @@ config :ex_dgraph, ExDgraph,
   # default port considered to be: 9080
   hostname: 'localhost',
   pool_size: 5,
-  max_overflow: 1,
   ssl: true,
   cacertfile: '/path/to/MyRootCA.pem',
   certfile: '/path/to/MyClient1.pem',

config/dev.exs

@@ -4,13 +4,4 @@ config :ex_dgraph, ExDgraph,
   # default port considered to be: 9080
   hostname: 'localhost',
   pool_size: 5,
-  max_overflow: 1,
-  # retry the request, in case of error - in the example below the retry will
-  # linearly increase the delay from 150ms following a Fibonacci pattern,
-  # cap the delay at 15 seconds (the value defined by the default `:timeout`
-  # parameter) and giving up after 3 attempts
-  retry_linear_backoff: [delay: 150, factor: 2, tries: 3],
   enforce_struct_schema: false
-
-# the `retry_linear_backoff` values above are also the default driver values,
-# re-defined here mostly as a reminder

config/test.exs

@@ -4,13 +4,5 @@ config :ex_dgraph, ExDgraph,
   # default port considered to be: 9080
   hostname: '0.0.0.0',
   pool_size: 5,
-  max_overflow: 1,
-  # retry the request, in case of error - in the example below the retry will
-  # linearly increase the delay from 150ms following a Fibonacci pattern,
-  # cap the delay at 15 seconds (the value defined by the default `:timeout`
-  # parameter) and giving up after 3 attempts
-  retry_linear_backoff: [delay: 150, factor: 2, tries: 3],
-  enforce_struct_schema: true
-
-# the `retry_linear_backoff` values above are also the default driver values,
-# re-defined here mostly as a reminder
+  enforce_struct_schema: true,
+  show_sensitive_data_on_connection_error: true

docker-compose-tls.yml

@@ -0,0 +1,42 @@
+version: "3.2"
+services:
+  zero:
+    image: dgraph/dgraph:v1.0.17
+    volumes:
+      - type: bind
+        source: ./dgraph_data
+        target: /dgraph
+        volume:
+          nocopy: true
+    ports:
+      - 5080:5080
+      - 6080:6080
+    restart: on-failure
+    command: dgraph zero --my=zero:5080
+  server:
+    image: dgraph/dgraph:v1.0.17
+    volumes:
+      - type: bind
+        source: ./dgraph_data
+        target: /dgraph
+        volume:
+          nocopy: true
+    ports:
+      - 8080:8080
+      - 9080:9080
+    restart: on-failure
+    command: dgraph alpha --my=server:7080 --lru_mb=2048 --zero=zero:5080 --tls_dir tls
+  ratel:
+    image: dgraph/dgraph:v1.0.17
+    volumes:
+      - type: bind
+        source: ./dgraph_data
+        target: /dgraph
+        volume:
+          nocopy: true
+    ports:
+      - 8000:8000
+    command: dgraph-ratel
+
+volumes:
+  dgraph:

docker-compose.yml

@@ -1,7 +1,7 @@
 version: "3.2"
 services:
   zero:
-    image: dgraph/dgraph:v1.0.16
+    image: dgraph/dgraph:v1.0.17
     volumes:
       - type: bind
         source: ./dgraph_data
@@ -14,7 +14,7 @@ services:
     restart: on-failure
     command: dgraph zero --my=zero:5080
   server:
-    image: dgraph/dgraph:v1.0.16
+    image: dgraph/dgraph:v1.0.17
     volumes:
       - type: bind
         source: ./dgraph_data
@@ -27,7 +27,7 @@ services:
     restart: on-failure
     command: dgraph alpha --my=server:7080 --lru_mb=2048 --zero=zero:5080
   ratel:
-    image: dgraph/dgraph:v1.0.16
+    image: dgraph/dgraph:v1.0.17
     volumes:
       - type: bind
         source: ./dgraph_data