import
filename
from
source
[alias
alias]
[options { ... }]
import
filename
source
custom_source
[alias
alias]
[options { ... }]
import
filename.ccr
source
custom_source
[alias
alias]
import ACCOUNT source
custom_source
[alias
alias]
import USAGE for
date
from
db_name
source
custom_source
[alias
alias]
\
- it is advisable to put the path and filename in double quotes to avoid the backslash being interpreted as an escape character=
sign is optional, but if present it must be surrounded by whitespace.import
are as follows:enabled
/ on
/ true
/ yes
enabled
/ on
/ true
/ yes
\
) characters in the data in the CSV to be imported as an escape character. This will escape the following delimiter or quote. For a literal backslash to be imported it needs to be escaped in the data (\\
). Where a backslash is not followed by another backslash or a quote, it is treated literally.enabled
/ on
/ true
/ yes
enabled
/ on
/ true
/ yes
enabled
/ on
/ true
/ yes
enabled
/ on
/ true
/ yes
EXIVITY_FILE_NAME
will be created which contains the filename from which each record was importedimport ACCOUNT source
custom_source
[alias
alias]
import USAGE for
date
from
dset
source
custom_source
[alias
alias]
yyyyMMdd
format. The RDF from which the usage will be imported is:<basedir>/system/report/<year>/<month>/<day>_<dset>_usage.rdf
.import USAGE for 20180501 from azure.usage source test alias data
<basedir>/system/report/2018/05/01_azure.usage_usage.rdf
test.data
.import
statement which are as follows:import
filename
from
source
[alias
alias]
<basedir>/system/extracted/<source>/<yyyy>/<MM>/dd>_.csv
_ portion of that filename and _
.csv` extension but an alias can be manually specified using the optional _alias parameter.20170223
, the statement:import usage from Azure
Azure.usage
from the file /system/extracted/Azure/2017/02/23_usage.csv
.import usage from Azure alias custom
Azure.custom
from the file<basedir>/system/extracted/Azure/2017/02/23_usage.csv
.import
filename
source
custom_source
[alias
alias]
.csv
extension but an alias can be manually specified using the optional alias parameter.20170223
, the statement:import "system/extracted/Azure/${dataDate}.csv" source Azure alias usage
Azure.usage
from the file<basedir>/system/extracted/Azure/20170223.csv
.ccr
filename extension as follows:"
- and a comma - ,
- respectively. Fields in the CCR file may or may not be quoted. The conversion process will handle this automatically and any quotes at the start and end of a field will be removed.import
are quote and separator (or delimiter). By default, these are set to a double quote and a comma respectively.embed
option is set, then a curly bracket in the data - {
- will cause all characters (including newlines) up until the closing bracket - }
- to be imported. Nested brackets are supported, although if there are an uneven number of brackets before the end of the line an error will be generated in the log file and the task will fail.Azure.usage
from the file /system/extracted/Azure/2017/02/23_usage.csv
import usage from Azure
Azure.custom
from the file /system/extracted/Azure/2017/02/23_usage.csv
import usage from Azure alias custom
Azure.usage
from the file /system/extracted/Azure/20170223.csv
import "system/extracted/Azure/${dataDate}.csv" source Azure alias usage
Azure.usage
from the file /system/extracted/Azure/20170223.csv
import "system/extracted/Azure/${dataDate}.csv" source Azure alias usage