You are not logged in.

nooby problem

Dear visitor, welcome to Palo Community Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

wudycool

Intermediate

  • "wudycool" started this thread

Posts: 10

Date of registration: Mar 18th 2009

  • Send private message

1

Monday, May 18th 2009, 7:47pm

nooby problem

Hallo Folks,
first im pretty new in paloETL.
i have some probleme to understand the manuel.
situation:
-----------
source_qube:
Qube_a:
dim1a
dim2a
dim3a
dim4a
dim5a
dim6a

target_qube:
Qube_b
dim1a
dim2a
dim3a
dim4a
dim1b
-----------
as u can see the qubes differ in number of dims but 4 dims are the same.

i want to write the value of
Qube_a[dim1a-dim4a].dim5a[root].dim6a[element1]

into the qube_cell

Qube_b[dim1a-dim4a].dim1b[element1]

next
step:
i want to write the value of Qube_a[dim1a.element(x).attribute1]

into

Qube_a[dim1a.element(x)].[dim2a-dim4a].[dim1b.element2]

hope everyone understands what i meen.

can someone show me how i have to write the pipeline?

This post has been edited 1 times, last edit by "wudycool" (May 18th 2009, 10:46pm)

wudycool

Intermediate

  • "wudycool" started this thread

Posts: 10

Date of registration: Mar 18th 2009

  • Send private message

2

Wednesday, May 20th 2009, 12:20pm

Please, need anyone with a hind...
Okay, ask me what u dont understand in my question and i will try to solve the problem.

This post has been edited 1 times, last edit by "wudycool" (May 20th 2009, 3:53pm)

wudycool

Intermediate

  • "wudycool" started this thread

Posts: 10

Date of registration: Mar 18th 2009

  • Send private message

3

Wednesday, May 20th 2009, 6:23pm

okay i tryed to write a little more:

Source code

 
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
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90

<?xml version ="1.0" encoding= "UTF-8"?>
<project name= "importolap" version="1.5">
<comment>
  Palo etl:test
</comment>
<connections>
  <connection name="palodemo" type="palo">
    <comment> paloquelldatenbank</comment> 
      <host>localhost</host>
        <port>7777</port>
        <user>admin</user>
        <password>admin</password>
     <database>Datenbank1</database>
    </connection>
  
</connections>
	<sources>
	   <source name="Qubequelle" type="OLAPCube">
	     <connection nameref="palodemo" />
	     <query>
	       <cube name="Qube1" />
	         <dimensions>
	           <dimension name="a1" leafs="restrict">
	           </dimension>
	           <dimension name="a2" leafs="restrict">
	           </dimension>
	           <dimension name="a3" leafs="restrict">
	           </dimension>
	           <dimension name="a4" leafs="restrict">
	           </dimension>
	           <dimension name="a5" leafs="root">
	           </dimension>
	           <dimension name ="a6" leafs="restrict">
	             <accept value="Element1" />
	           </dimension>
	         </dimensions>
              </query>
	     </source>
	      <source name="sourceb1" type="OLAPDimension">
    			<connection nameref="palodemo" />
    			<query>
    	       		    <dimension name="b1" leafs="restrict">
    					
			    </dimension>
			 </query>
		</source>
	    </sources>
	    <pipelines>
	     <pipeline name="erg" type="Table">
	       <sources>
	         <source nameref="Qubequelle" />
	         <source nameref="sourceb1" />
	       </sources>
	       <target>
	       <coordinates>
                <coordinate name="a1">
                 <input nameref="a1" />
                </coordinate>
                <coordinate name="a2">
                 <input nameref="a2" />
                </coordinate>
                <coordinate name="a3">
                 <input nameref="a3" />
                </coordinate>
                <coordinate name="a4">
                 <input nameref="a4" />
                </coordinate>
                <coordinate name="b1">
                 <input nameref="b1" />
                </coordinate>
              </coordinates>
	     </target>
	    </pipeline>
	  </pipelines>
	    
	  <exports>
	     <export name="targetqube" type="Cube"  mode="create">
	         <connection nameref="palodemo" />
	      
	         <source nameref="erg" />
	     </export>
	  </exports>
	    
	 <jobs>
	     <job name="Cube_ziel">
	       <export nameref="targetqube" />
	     </job>
	 </jobs> 
	    
	  </project>


this dosent work becouse can not bind to input "b1" in pipeline.
i think i have a mayor understanding problem with pipelines and target i dont know how i can write the value in quellqube{[a1].[a2].[a3].[a4].[a5].[a6.element1]} into targetqube{[a1].[a2].[a3].[a4].[b1.Element]} becouse i dont know how do i refer a6.element1 with b1.Element

This post has been edited 1 times, last edit by "wudycool" (May 20th 2009, 6:30pm)

kais

Master

Posts: 64

Date of registration: Mar 4th 2009

  • Send private message

4

Friday, May 22nd 2009, 3:00pm

Hello

Regarding this part:

source_qube:
Qube_a:
dim1a
dim2a
dim3a
dim4a
dim5a
dim6a

target_qube:
Qube_b
dim1a
dim2a
dim3a
dim4a
dim1b

What you should think of is what logic I want to use to add the dimension in the cube? should the value from the smaller cube (only dim1a-dim4a) splashed over all the cells of the newer dimension? You can not simply say I want to add a dimension without saying how the new input should be integrated in the new cube.

reducing the 6-dim cube to a 4-dim cube is on the other hand relatively straightforward in ETL. Check table pipeline to see how exactly (or importRelDB.xml)

Regards,
Kais

wudycool

Intermediate

  • "wudycool" started this thread

Posts: 10

Date of registration: Mar 18th 2009

  • Send private message

5

Tuesday, June 2nd 2009, 4:06pm

Hallo, i fond a workaround, i do the import with palo importer until i understand etl-xml ;) but maybe this workaround help u guys to understand what i wont to do.

Source code

 
1
2
3
4
5

okay i use the normel palo importer with the cube_a. 
it goes through all cell in the first row and i use the "palo.setdata"-function like this:
paloimport raw:dim1a|dim2a|dim3a|dim4a|dim5a(root)|dim6a(element1)|value

Palo.setdata=PALO.SETDATA(VALUE;WAHR;"databank";Cube_b;dim1a;dim2a;dim3a;dim4a;"dim1b.element_X";)


this does exactly what i want but i want to do this with palo-etl.
hope someone can help me.

wudycool

Intermediate

  • "wudycool" started this thread

Posts: 10

Date of registration: Mar 18th 2009

  • Send private message

6

Tuesday, June 2nd 2009, 8:08pm

here an easyer example of what i want.

Source code

 
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

<?xml version ="1.0" encoding= "UTF-8"?>
<project name= "test" version="1.1">
<comment>
  Palo etl: rudimenterer test mit einer test db und 3 dimensionen in einen cube mit 2 dims umwandeln
</comment>
<connections>

    <connection name="umwandlertest" type="palo">
      <comment> localtest db </comment>
      <host>localhost</host>
      <port>7777</port>
      <user>admin</user>
      <password>admin</password>
      <database>localtest</database>
    </connection>
  
</connections>
    <sources>
      <source name="Qubequelle" type="OLAPCube">
	      <connection nameref="umwandlertest" />
	         <query>
	         <cube name="test" />
	         <dimensions>
	           <dimension name="dim1" leafs="restrict">
	             <accept value="Alle" />
	           </dimension>
             <dimension name="dim2" >
	           </dimension>
	           <dimension name="dim2" >
	           </dimension>
	           
	         </dimensions>
	        </query>
	    </source> 
	  </sources>
	    <pipelines>
	     <pipeline name="erg" type="Table">
	       <sources>
	         <source nameref="Qubequelle" />
	       </sources>
	     <target>
	       <coordinates>
	       <coordinate>
			<input nameref="dim1" />
		</coordinate>
					
		<coordinate>
			<input nameref="dim2" />
		</coordinate>
		
					
		</coordinates>

//SOMETHING IS MISSING HERE(measure?? im realy confused...), BUT I DONT KNOW WHAT..., i know this is not the right way, now i ask for help to find the right way to solve this problem(ashamed)

Source code

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

	    </target>
	    </pipeline>
	   </pipelines>
	   
	  <exports>
	     <export name="test2" type="Cube"  mode="create">
	         <connection nameref="umwandlertest" />
	      
	         <source nameref="erg" />
	     </export>
    </exports>
	  <jobs>
	     <job name="Cube_ziel">
	       <export nameref="test2" />
	     </job>
    </jobs>	   
</project>


ps: i realy dont know why i have such a big problem with palo etl... i do not see the forest for the trees

This post has been edited 1 times, last edit by "wudycool" (Jun 2nd 2009, 8:12pm)

a_froehlich

Sage

Posts: 173

Date of registration: Jan 4th 2008

Location: Freiburg / Germany

  • Send private message

7

Wednesday, June 17th 2009, 7:53am

Some remarks which might be helpful for you:

1. "How do i refer a6.element1 with b1.Element". This can be done with a constant input in Table-Pipeline/Transform:
<coordinate name="b1">
<input constant="Element" />
</coordinate>

2. In the Table-Pipeline you need an additional coordinate for the cell value of the Input-Cube:
<coordinate>
<input nameref="#Value" />
</coordinate>
</target>
</pipeline>

3. The Source Reference of 2 Sources from type OLAPCube and OLAPDimension is not reasonable. "sourceb1" should be removed here:
<pipeline name="erg" type="Table">
<sources>
<source nameref="Qubequelle" />
<source nameref="sourceb1" />
</sources>
<target>
Rate this thread