- #MAILSPRING CONFIG.JSON LOCATION HOW TO#
- #MAILSPRING CONFIG.JSON LOCATION CODE#
- #MAILSPRING CONFIG.JSON LOCATION PLUS#
In this case there are no conversions necessary for the time_column_format as it is formatted in the original data, so we input the same value in the conversion_params field.
![mailspring config.json location mailspring config.json location](https://images-na.ssl-images-amazon.com/images/I/A1OGTc%2BfFzL.png)
You then have the opportunity to use the columns object to identify the column name, data type, and any conversion parameters. In the example below we’re identifying timeStamp as our primary timestamp column and we’re identifying user_id from the data set as our shard key. The columns object serves the purpose of identifying key parameters about the timestamp and shard keys input in the table object from step 4 and 5 above. This is the data on which you want to perform your analysis. A shard key is a column in your dataset that represents an important entity that the event is about. When you initially create your table, the only columns defined are the time column and shard key columns. Scuba does not support dates prior to Janu(the beginning of Unix epoch time). Note that for a given column in your data, the time format must remain consistent for every event.
#MAILSPRING CONFIG.JSON LOCATION PLUS#
If your timestamps do not follow the ISO-8601 standard or you cannot reformat your timestamps to follow the standard, Scuba also supports Unix time plus a variety of common strptime() time format strings. If your Timestamp Format is not already in epoch milliseconds or seconds, Scuba requires that you format your timestamp data according to the ISO-8601 standard. If your timestamp is already in epoch seconds or milliseconds input "time_column_format": "milliseconds" or "time_column_format": "seconds" Every table imported into Scuba requires a timestamp. This input will be the exact name of the primary timestamp column in the Event table. Scuba can ingest both Event and Lookup tables. The name you assign to a table is how it will appear in the Scuba UI, and will be used to differentiate from other tables. The necessary configuration parameters to create a table with the config.json file are: In Scuba, a table refers to the contents of a database table, where each column represents a particular variable, and each row corresponds to a given member of the dataset. You begin the ingest process by creating a table.
![mailspring config.json location mailspring config.json location](https://papunika.com/wp-content/uploads/2021/04/location_starlight_lighthouse_island2-1024x783.jpg)
#MAILSPRING CONFIG.JSON LOCATION HOW TO#
Read on to learn how to edit a config.JSON file for Scuba Lite Import.ĬODE Editing A Config File For Scuba Import Creating A Table For any clarification on the terminology mentioned in this guide, please visit our guides and glossary. The file name can be unique however it requires the config.json extension for import to work successfully (example: myDataSet_config.json).
![mailspring config.json location mailspring config.json location](http://orcz.com/images/6/6a/Redoransretreatworldmap.jpg)
#MAILSPRING CONFIG.JSON LOCATION CODE#
Copy and paste the code snippet below and save it locally as config.json. What You Should Know About Structuring Your Dataīelow is a sample Config.JSON file, which you will need during the import process for implementing Scuba Lite. For any questions please reach out to Talk to an Expert.īest Practices for Formatting Data for Ingest You can also refer to our Scuba Lite Data Import document for more information and the resources below before moving forward with importing data. Please read our Data Set Requirements Checklist before moving forward. Before importing data into Scuba it is important to know the types of data that work best with scuba.