Skip to content

Commit

Permalink
added clarity to readme
Browse files Browse the repository at this point in the history
  • Loading branch information
Gary Arora committed Apr 5, 2020
1 parent 5bb04f8 commit 704ae9b
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Expand Up @@ -120,7 +120,7 @@ const aws = require("aws-sdk");
//Advance configuration with all options
const athenaExpressConfig = {
aws, /* required */
s3: "STRING_VALUE", /* optional */
s3: "STRING_VALUE", /* optional format 's3://bucketname'*/
db: "STRING_VALUE", /* optional */
workgroup: "STRING_VALUE", /* optional */
formatJson: BOOLEAN, /* optional default=true */
Expand All @@ -139,9 +139,9 @@ const athenaExpress = new AthenaExpress(athenaExpressConfig);

| Parameter | Format | Default Value | Description |
| ------------- | ------------- | ------------- | ------------- |
| s3 | string | `athena-express` creates a new bucket for you | S3 bucket name/prefix to store Athena query results |
| s3 | string | `athena-express` creates a new bucket for you | The location in Amazon S3 where your query results are stored, such as `s3://path/to/query/bucket/`. <br /> `athena-express` will create a new bucket for you if you don't provide a value for this param but sometimes that could cause an issue if you had recently deleted a bucket with the same name. (something to do with cache). When that happens, just specify you own bucket name. Alternatively you can also use `workgroup`. |
| db | string | `default` | Athena database name that the SQL queries should be executed in. When a `db` name is specified in the config, you can execute SQL queries without needing to explicitly mention DB name. e.g. <br />` athenaExpress.query("SELECT * FROM movies LIMIT 3")` <br /> as opposed to <br />` athenaExpress.query({sql: "SELECT * FROM movies LIMIT 3", db: "moviedb"});` |
| workgroup | string | `primary` | The name of the workgroup in which the query is being started. |
| workgroup | string | `primary` | The name of the workgroup in which the query is being started. <br /> Note: athena-express cannot create workgroups (as it includes a lot of configuration) so you will need to create one beforehand IFF you intend to use a non default workgroup. Learn More here. [Setting up Workgroups](https://docs.aws.amazon.com/athena/latest/ug/user-created-workgroups.html) |
|formatJson | boolean | `true` | Override as false if you rather get the raw unformatted output from S3. |
|retry | integer | `200` milliseconds| Wait interval between re-checking if the specific Athena query has finished executing |
|getStats | boolean | `false`| Set `getStats: true` to capture additional metadata for your query, such as: <ul><li>`EngineExecutionTimeInMillis`</li><li>`DataScannedInBytes`</li><li>`TotalExecutionTimeInMillis`</li><li>`QueryQueueTimeInMillis`</li><li>`QueryPlanningTimeInMillis`</li><li>`ServiceProcessingTimeInMillis`</li><li>`DataScannedInMB`</li><li>`QueryCostInUSD`</li><li>`Count`</li><li>`QueryExecutionId`</li><li>`S3Location`</li></ul> |
Expand Down

0 comments on commit 704ae9b

Please sign in to comment.