Latest release (1.4.0) not working if athenaclirc file not in path
See original GitHub issueathenacli works with version 1.3.3, but I get this message when trying to run athenacli 1.4.0:
Required argument `s3_staging_dir` or `work_group` not found.
There was an error while connecting to AWS Athena. It could be caused due to
missing/incomplete configuration. Please verify the configuration in ~/.athenacli/athenaclirc
and run athenacli again.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Package List — Spack 0.20.0.dev0 documentation
This is a list of things you can install using Spack. It is automatically generated based on the packages in this Spack version....
Read more >pyathena - PyPI
PyAthena is a Python DB API 2.0 (PEP 249) compliant client for Amazon Athena. Requirements. Python. CPython 2,7, 3,4, 3.5, 3.6 ...
Read more >Index of Portage & Programming - Gentoo Forums
Index of Portage & Programming. "Allow remote access to mySQL" Page:1 · "binary packages for different use flags?" Page:1 · "Question about LVM2...
Read more >`Spaceship::PortalClient#associate_groups_with_app` results ...
That said, I am able to successfully associate app groups to my app when using Spaceship::Portal . This behavior is not consistent though....
Read more >npmsearchfullcat_npm143.txt - GitHub
JS API Example =vertexclique 2013-11-09 0.0.1 airve static latest version URIs for ... animator Hook into request animation frame or setInterval if rAF...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I will create a new release tonight. Thank you so much for fixing it.
Fixed in release v1.4.1. I also did some minor changes. Feel free to reopen this if you the issue still exists.