new branch after 5.0 release
[MONDRIAN-1703]  Determination of the aggStar in SqlTupleReader is independent of the determination of the measures present in a native filter.  This left open the possibility that
one or more measures could be missing from the aggregate table that was selected, since only one of the measures is set in context.
E.g. filter (<set>, measure.[a] > measure.[b]) can be natively evaluated only if the columns for both measure [a] and [b] are present in the agg table.
To side step the issue, this fix omits the having constraint if we determine that a measure is not present.
(cherry picked from commit c6f0d81)
[MONDRIAN-1703]  Added one more test query to verify the negative case.
(cherry picked from commit c7c285e)
Merge pull request #143 from mkambol/3.6-mon1703

MONDRIAN-1703] Determination of the aggStar in SqlTupleReader is ind…
[MONDRIAN-1512]  Correcting the inline SQL used by Impala.
(cherry picked from commit 2d37427)
Merge pull request #144 from mkambol/3.6-mon1512

[MONDRIAN-1512]  Correcting the inline SQL used by Impala.
[MONDRIAN-1729][SP-632]  "Query required more than 12 iterations" error when query should complete.

This change addresses a case where the ordering in which segments are processed by SegmentBuilder.rollup() could impact the resulting segment.  In some cases,
if a column of the second axis was wildcarded, it could incorrectly result in the axis being set as having incompatible predicates (lostPredicate=true).  Similarly,
the intersecting values could be mishandled, depending on the ordering of segments with wildcarded columns.
Test cases committed with this change check for equivalent rollups with segments processed in forward and reverse order.
(cherry picked from commit 2cdffbe64ee6a9e46ce9f4c084ab547e1786ed54)
[MONDRIAN-1729][SP-632] Missed a case where the first header loaded (used for initializing the AxisInfo) contains a wildcarded column that should be downgraded to
a specific list when computing segment intersection.
(cherry picked from commit 25eba12)
[MONDRIAN-1729][SP-632]  Made the segments list an UnmodifiableArrayList.
(cherry picked from commit 76eb9a3)
Merge pull request #163 from mkambol/SPmon1729

[MONDRIAN-1729][SP-632] "Query required more than 12 iterations" error
Create tag from build job 'mondrian-schema-workbench' #38, source branch '3.6'
Update versions for SNAPSHOT builds
Update build.properties
[MONDRIAN-1726]  Possible deadlock when number of batches exceeds available connections in the pool

Deadlock could occur if a cardinality query occurred on the actor thread when all db connections were consumed.  See the details of MONDRIAN-1726 for details about
the exact scenario.

This change forces cardinality values to be loaded before issuing a LoadBatchCommand, avoiding the risk of a query happening on the thread.  The down side of this approach
 is that cardinality checks are performed even in some cases where they wouldn't be necessary.  MONDRIAN-1801 is intended to come up with a better solution for Mondrian 4.
(cherry picked from commit 5a81dc3)
[MONDRIAN-1726]  Eliminated RolapUtil.Semaphore in favor of java.util.concurrent.Semaphore.  Our home-rolled version had bugs that show up when testing with low QueryLimit values.
(cherry picked from commit a64898c)
[MONDRIAN-1785] Backport of commits 00e3d2bc6c376311ff6b2e5b6628564a45ce233f a3012a4d5e8beb7e7335312f7585cafa72ca4729 75bc4975ffbddb56fbeaab0f36923dd34c76ca1d form master.
(cherry picked from commit 3e11ff5)
Merge pull request #195 from mkambol/cherryPick

[MONDRIAN-1726][MONDRIAN-1785]  Cherry pick of commits from master for SP.
[PDI-11024] Removes a method which should not have been checked into the code. Was fixed on master but not on 3.6.
[MONDRIAN-1867] Syntax error using aliases in the order by clause with Mondrian SQL generated against DB2

Change a3012a4 corrected an issue where the alias was not used in the ORDER BY even if requiresOrderByAlias was true for a dialect.
Once that was fixed DB2, ORDER BY queries started failing.  From tests against DB2 10.2 it appears aliases are permitted in the ORDER BY clause only if they are
*unquoted* in the SELECT list.  But expressions are also permitted, so requiresOrderByAlias can be set to false.
(cherry picked from commit b42fecc)
SP-1003 - MONDRIAN-1615 - removing tuples that contain hidden members from native tuple results. cherry-picked from 09217f6906ce35eaaca4581a20f0e993b1cc8ba6