Grzegorz Kokosiński
Grzegorz Kokosiński
That way a `FailsafeException` will contain all information about all attempts. See: https://docs.oracle.com/javase/7/docs/api/java/lang/Throwable.html#addSuppressed(java.lang.Throwable)
There are things in presto configuration which can be set differently on each node. For example `node.id` in `node.properties` or `node.internal-adress` in `config.properites`. The idea is to support template configuration...
It would be nice that prestoclient.py would be extracted as separate tool that could be: 1. used from other python libs (tools) 2. tested there thoroughly as current test_prestoclient.py does...
In my opinion, when testing if given properties are defined in properties file should ignore the order in which properties are defined. The best would be to compare properties which...
tox requires that development workstation is equipped with two python installations (2.6 and 2.7). However it could be somehow difficult to achieve as some linux distribution no longer support usage...
Currently product tests create a docker image which then is reused by subsequent tests. The next product tests execution will reuse previously created images disregarding that product (presto admin package)...
Code under https://github.com/prestodb/presto-admin/blob/master/tests/product/prestoadmin_installer.py#L80 should be extracted as some `make build` command. Thanks to that user (developer) has a control when a package is rebuilt. Currently it rebuilds automatically, which is...
Each build should push docker image with presto-admin installed into docker-hub under `teradata-labs` organization so user can easily install Presto on docker cluster. This could be done automatically by travis....
It would be nice to track all the changes to presto cluster. So user can: - see history of configuration changes (like change in node.properties file or new presto version...
https://github.com/prestodb/presto/pull/7467