Ryan, if you hadn't told us that you were putting them already in a database I'd have suggested you should;-)
Things being as they are (TM1Server v11 and before) queries against the transaction log are contentious (effectively block any other commits). The occasional brief query doesn't hurt as (hence: why I did a special implementation for deltas) but longer running queries could, especially with larger transaction logs, seriously impact the system.
We contemplated at some point to allow users to see their own transactions (like we do in the REST API for the threads/sessions) but shed away from doing so for the exact same reason, not wanting to invite clever people to add contention to the most contentious resource we have.
So, for now, I'd indeed put it in a separate database and, if I was writing my own client, I wouldn't even use TM1's drill through as the middle man but directly go to that database to retrieve the transactions I'd be looking for. Any reason why you wouldn't?
Now the 'good' news perhaps is that in the next major version of TM1 server we already have these transactions in a database (part of the high availability work we've been working on for a while). We have not finalized any new APIs for that version, might not need any, but at least we'll have tackled the contention issues plus the performance presumably would be way better than ploughing through old fashion text files;-).
------------------------------
Hubert Heijkers
------------------------------
Original Message:
Sent: Wed January 08, 2020 03:02 PM
From: Ryan Clapp
Subject: REST - FilterableProperties on TransactionLogEntries
Today we extract transactions, push them into a database, and then expose them via drill through. There is an inherent time lag due to the length of the processing. In our UI we want users to be able to right click on a data point, cell in a view, and select an option to "Show all Changes".
Original Message------
Hi Ryan,
Interesting question...Not currently possible and it's not on our roadmap. Why do users need to see transactions? Is it transactions for all users or just the data changes made by the user running the query?
I think we do want to look into storing transactions in proper database at some point in the distant (or maybe not so distant) future. We might look at security for transactions at that point. We won't plan any changes in security in this area in the current version of TM1 Server.
------------------------------
Stuart King
IBM Planning Analytics Offering Manager
------------------------------
#PlanningAnalyticswithWatson