-
Notifications
You must be signed in to change notification settings - Fork 14
/
Copy path1-files-for-testing.sql
58 lines (42 loc) · 1.63 KB
/
1-files-for-testing.sql
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
-- Description:
-- In this example we show how you can manage file
-- orchestration using Luminesce. If a response/table
-- has errors, we move the file to an "error" directory.
-- If the response/table has no errors, we move the file to
-- a "processed" directory
@@successFileName1 = select 'instruments_success_001';
@@successFileName2 = select 'instruments_success_002';
@@successFileName3 = select 'instruments_success_003';
@@errorFileName1 = select 'instruments_error_001';
@@newDirectory = select 'luminesce-examples/orchestration/new';
/*
==============================================
1. Create files for testing
==============================================
*/
@successFile1 = select 'BondA' as 'InstrumentId',
0 as WriteErrorCode, @@successFileName1 as FileName;
@successFile2 = select 'BondB' as 'InstrumentId',
0 as WriteErrorCode, @@successFileName2 as FileName;
@successFile3 = select 'BondC' as 'InstrumentId',
0 as WriteErrorCode, @@successFileName3 as FileName;
@errorFile1 = select 'BondD' as 'InstrumentId',
105 as WriteErrorCode, @@errorFileName1 as FileName
union
values
('BondE', 0, 'instruments_error_001.csv');
/*
==============================================
2. Save new file to Drive
==============================================
*/
@saveFilesToDrive = use Drive.SaveAs with @successFile1, @successFile2, @successFile3, @errorFile1, @@newDirectory
--path=/{@@newDirectory}
--ignoreOnZeroRows=true
--fileNames
instruments_success_001
instruments_success_002
instruments_success_003
instruments_error_001
enduse;
select * from @saveFilesToDrive;