Mondrian | A static php code analysis tool using the Graph Theory

You can use $group stage after $match stage,

• $group by url and get first root document using $$ROOT, this will return document in root field

As the Pentaho Analizer Cookbook specifies, that Formula is for pinning a Measure to a certain level.

It is: if you drill-down, you'll get the value as the drill-up.

If what you need (if I understood correctly) is to just display nothing for upper-levels, then user the next Formula:

IIF([Dimensions].CurrentMember.Level.Ordinal < 3 , NULL , [Measures].[My measure] )

You're close:

Add a second HierarchyGrant to restrict its visibility, such as:

If anyone stumble with this question, then, you're likely making the same mistake as I am:

After quite some hours comparing other folks' Mondrian schemas with mine, and having a look at the book "Mondrian in action", I realized I was making a total misuse of the parentColumn, which is (I think) aimed to point to the same hierarchy level, such as in employees with supervisors that are also employees.

The solution is to completely remove parentColumn property of the xml.

The test MDX query does not specify the slicer (WHERE clause). In this case the slicer is created automatically and includes all dimensions which are not mentioned on other axis. Moreover slicer is built with default dimension elements. As you have not specified any default members when defining dimension, Mondrian just takes the "first" element. What is the first element can be determined by the dimension ordinal (or sorting of the dimension elements). So I guess Mondrian just gets the "null" element as the first element in the dimension. I would suggest to adjust your Mondrian schema so that each dimension has a default order and perhaps add some filters to exclude NULL element values.

For me (also Ubuntu 18.04), the path of the installation directory is: /usr/lib/python3/dist-packages/pygments. There you will find another directory named styles where all the existing color themes are present (e.g. autumn.py, fruity.py). You may create your own style (following: https://pygments.org/docs/styles/) and store the corresponding style file here.

I hope this partially answers your query.

As there's only a limited supply of colors, and each line should have it's own, the modulo operator seems fitting:

instead of using request.data try

req_body = json.loads(request.body.decode('utf-8'))

and then you can use req_body like dict in python

You will find below description from pentaho docs

1. To create a new Mondrian schema, click the New button, or go to the File menu, then select New, then Schema. A new schema sub-window will appear. Resize it to fit your preference.
2. It's easier to visualize your physical data model if you have it in front of you. Turn on the JDBC Explorer from the New section of the File menu and position it according to your preference. If you have a third-party database visualization tool that you are more familiar with, use that instead. The JDBC Explorer is not interactive; it only shows the table structure of your data source so that you can see at a glance what the names of the columns and rows in it.

3. Typically your first action when creating a schema is to add a cube. Right-click the Schema icon in the schema window, then select Add cube from the context menu. Alternatively you can click the New Cube button in the toolbar. A new default cube will show up in your schema.

4. Add a table by clicking the New Table button, or by right-clicking your cube, then selecting Add Table. This will be your fact table. Alternatively you can select View or Inline Table if these are the data types you need for your fact table.

5. Click the Table entry in the name field of your new table, and select or type in the name of the table in your physical model that you want to use for this cube's fact table.
6. Add a dimension by right-clicking the cube, then selecting Add Dimension, or by clicking the New Dimension button.
7. When you add a dimension, a new hierarchy is automatically created for it. To configure the hierarchy, expand the dimension by clicking the lever icon on the left side of the dimension's tree entry, then click on New Hierarchy 0. Choose a primaryKey or primaryKey Table.
8. Add a table to the hierarchy by right-clicking the hierarchy, then selecting Add Table from the context menu.
9. Add a level to the hierarchy by right-clicking the hierarchy, then selecting Add Level from the context menu.
10. Add a member property to the level by right-clicking the level, then selecting Add Property from the context menu.

11. Add a measure to the cube by right-clicking the cube and selecting Add Measure from the context menu.

12. Choose a column that you want to provide values for, then select an aggregator to determine how the values should be calculated.

    These instructions have shown you how to use Schema Workbench's interface to add and configure basic Mondrian schema elements.

pentaho docs