forked from olap4j/olap4j-xmlaserver
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathCHANGELOG
54 lines (45 loc) · 1.65 KB
/
CHANGELOG
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
==2014-05-22==
* Habe repository geforkt:
** git remote add fork https://github.com/bkaempgen/olap4j-xmlaserver.git
* Anschließend aktuellen Stand überschrieben:
** git push -f fork master
* Version ist:
<pre>
commit e444eae9a5eadec7c4d718f757f65c02534b5121
Author: benedikt <[email protected]>
Date: Thu May 22 19:09:45 2014 +0200
My own version that is working.
commit de093d292118c4b62e596a04e865070fa8772fcc
Merge: a37547e dad5a17
</pre>
* Nun möchte ich Updaten auf neueste Version, aber auch wieder zurück kommen können auf meine Version.
==Status 2013-07-07==
* Problem: Apparently, since cube name pattern (restrictions) is a wildcard, a list of values is stored. Therefore,
when querying for cubes in xmla-server, I check whether restrictions is a list:
<pre>
// Get cube manually
Iterable<Cube> cubelist;
// We have to consider that with xmla4js, this always is a list.
String cubename;
if (this.restrictions
.get("CUBE_NAME") instanceof List) {
List cuberestrictionlist = (List) this.restrictions
.get("CUBE_NAME");
cubename = cuberestrictionlist.get(0).toString();
} else {
cubename = this.restrictions
.get("CUBE_NAME").toString();
}
if (cubename != null) {
Cube mycube = schema.getCubes().get(
cubename);
ArrayList<Cube> newlist = new ArrayList<Cube>();
newlist.add(mycube);
cubelist = newlist;
} else {
cubelist = filter(sortedCubes(schema), cubeNameCond);
}
</pre>
==Status 2013-07-08==
* xmla-server would not add proper restrictions to discover requests which would not allow olap4ld
to know the cube to query. (in RowsetDefinition).