0.48 RC - end of activity and log tables!

Feature Requests
21

What I do to keep history :

CREATE TABLE mydb.metabase_query_execution LIKE metabase.query_execution;
INSERT INTO mydb.metabase_query_execution TABLE metabase.query_execution;

CREATE EVENT upkeep_metabase_query_execution
ON SCHEDULE EVERY 1 HOUR STARTS '2024-01-05 03:00:00'
DO 
INSERT IGNORE INTO mydb.metabase_query_execution
SELECT ALL *
FROM metabase.query_execution
WHERE started_at > (SELECT ALL MAX(started_at) FROM mydb.metabase_query_execution);
22

It appears there is no reconsideration on this topic within the Metabase team.

We extensively use these tables to understand our stakeholders’ usage, which in turn helps us increase Metabase usage. Therefore, it could be viewed as a “win-win” strategy for both Metabase and OSS users like us. As mentioned in many earlier posts, retention could easily be limited.

Please reconsider this decision.

2 Likes
23

Open Source plan is "Free Forever" but there is no statement that some functionality will not be removed, I'm afraid of what they will remove next time :slightly_frowning_face:

2 Likes
24

I think we can still use query_execution table to replace what view_log table can do, right?

25

Do you don't have user info there, in view_log table @abed.1

26

If showing up with my frustration makes something… here I am!

I am also a Metabase PRO user with use case of having OSS; and it’s a shame this kind of decision.
I cannot even demonstrate the fact of: yes, we need to upgrade to PRO because see how many users we have that will take of PRO advantages.

Please reconsider!

1 Like