for now it is research into the tooling
I had a look at bubbles, metl (very short at petl and pygraml and bonobo)
I think I will use bubbles for the proof of concept and then have a second look at the above other tools#
proof of concept means: I am building a analytics db with cubes and use bubbles to get some initial data into it
when i run "slicer serve slicer.ini" i ge below error
- Restarting with stat
File "C:\Users\krishna\AppData\Local\Programs\Python\Python36\Scripts\slicer.exe", line 1
SyntaxError: Non-UTF-8 code starting with '\x90' in file C:\Users\krishna\AppData\Local\Programs\Python\Python36\Scripts\slicer.exe on line 1, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details
Plz help
Anyone still active about cubes? I need help!
e.g. i want to calculate the difference between subsequent rows via a window function:
{
'name': 'revenue_change',
'expression': "(lead(coalesce(sum(pl.revenue), 0)::integer, 1, 0) OVER (ORDER BY month_end DESC) - coalesce(sum(pl.revenue), 0)) AS delta"
}
I don't know if there is some standard for that at any level. In the OLAP materials I've read that need is not usually even mentioned, or is left up to the reporting/visualization tool. Also afaik standards like MDX don't contemplate that explicitly, besides allowing subqueries.
and a cube defined as
"cubes": [
{
"name": "posts_to_social",
"label": "Posts to Social Media",
"dimensions": ["site", "social_provider", "posted_at"],
"aggregates": [
{
"name": "record_count",
"function": "count"
}
],
"mappings": {
"posted_at.year": {"column":"posted_at", "extract":"year"},
"posted_at.quarter": {"column":"posted_at", "extract":"quarter"},
"posted_at.month": {"column":"posted_at", "extract":"month"},
"posted_at.week": {"column":"posted_at", "extract":"week"},
"posted_at.day": {"column":"posted_at", "extract":"day"}
},
"joins": [
{"master":"site_id", "detail":"site.site_id"}
]
}
],
"dimensions": [
{ "name": "site", "attributes": ["site_id", "name"] },
{ "name": "social_provider" },
{ "name": "posted_at",
"label": "Posted",
"template": "date",
"order": "desc"
},
{
"comment": "This is used as a template for other date dimensions.",
"name": "date",
"label": "Date",
"role": "time",
"levels": [
{
"name": "year",
"order": "desc",
"order_attribute": "year",
"label": "Year"
},
{
"name": "quarter",
"label": "Quarter",
"order_attribute": "quarter",
"order": "desc"
},
{
"name": "month",
"label": "Month",
"order_attribute": "month",
"order": "desc"
},
{
"name": "week",
"label": "Week",
"order_attribute": "week",
"order": "desc"
},
{
"name": "day",
"label": "Day",
"order_attribute": "day",
"order": "desc"
}
],
"hierarchies": [
{
"name": "weekly",
"label": "Weekly",
"levels": ["year", "week"]
},
{
"name": "monthly",
"label": "Monthly",
"levels": ["year", "quarter", "month"]
},
{
"name": "daily",
"label": "Daily",
"levels": ["year", "month", "day"]
}
]
}
]
}
however the sorting is rather 'abritrary'
sp? @Vkynluv
I think as an alternative approach you could define a view that calls the stored procedure
[Store]
url : mssql+pyodbc://Username:Password@Host:Port/DbName?driver=SQL+Server+Native+Client+11.0
url : mssql+pyodbc://Username:Password@Host:Port/DbName?driver=SQL+Server+Native+Client+11.0
You cannot call a stored proc from inside a view. It is not supported. However you can make views call other views, or table-valued user-defined functions.
how good are your AngularJS skills?
also I cannot see the order by in the SQL:
DEBUG SQL(aggregation drilldown):
SELECT EXTRACT(year FROM posts_to_social.posted_at) AS "posted_at.year", EXTRACT(quarter FROM posts_to_social.posted_at) AS "posted_at.quarter", EXTRACT(month FROM posts_to_social.posted_at) AS "posted_at.month", count(posts_to_social.id) AS record_count
FROM posts_to_social GROUP BY EXTRACT(year FROM posts_to_social.posted_at), EXTRACT(quarter FROM posts_to_social.posted_at), EXTRACT(month FROM posts_to_social.posted_at)
or the get request:
"GET /cube/posts_to_social/aggregate?drilldown=posted_at%40monthly%3Amonth HTTP/1.1"