I'm new to Superset and I don't know how to prevent my dashboard from refreshing every time it is opened.
I don't need it because in the database I'm using the data is inserted once a day and I've set the auto refresh interval to 24 hours. Also, the queries are quite complex so the charts take quite a long time to load.
I've searched the docs and found nothing about this issue.
A default installation of SuperSet does not have caching enabled by default. You should enable caching so that a query is not fired everytime the dashboard is viewed. It's possible to define global level caching strategy and also have dashboard specific overrides.
https://superset.apache.org/docs/installation/cache
Related
Please, I created this report and published it on the web
But it is interesting that the filters that I enabled in three columns do not appear - they only work on my computer, in the desktop version. Does Publishing to the Power BI Web not allow you to include filters?
Filters should work the same with Publish to Web.
One thing you need to keep in mind is that there can be a significant lag between publishing the file and when the public link is updated.
From Microsoft documentation:
How it works (technical details)
When you create an embed code using Publish to web, the report is made visible to Internet users. It's publicly available, so you can expect viewers to easily share the report through social media in the future. Users view the report either by opening the direct public URL or viewing it embedded in a web page or blog. As they do, Power BI caches the report definition and the results of the queries required to view the report. This caching ensures that thousands of concurrent users can view the report without impacting performance.
The data is cached for one hour from the time it is retrieved. If you update the report definition (for example, if you change its View mode) or refresh the report data, it can take some time before changes are reflected in the version of the report that your users view. When a data refresh occurs for an import data model, the service clears the cached data and retrieves new data. In most cases, the data is updated nearly simultaneous with the import of the data. However, for reports with many distinct queries, it may take some time to update. Since each element and data value is cached independently, when a data update occurs, a user may see a mix of current and previous values. Therefore, we recommend staging your work ahead of time, and creating the Publish to web embed code only when you're satisfied with the settings. If your data will refresh, minimize the number of refreshes and perform the refreshes at off hours. We don’t recommend using Publish to web for data that needs to refresh frequently.
Make sure you have the Filtering enabled in the 'Options and settings' section of the Desktop PBI before publishing.
Screenshot Attached
I am looking for the solution for Spotfire Webplayer Auto Refresh for version 6.5.2
I am aware of a similar question being asked in the forum, but the answer has not been able to resolve my query.
What I have done:
I have the information link connected to a Oracle table and this Information link is being reloaded periodically every 5 minutes.( The solution in the previous posts).
The users are logging into the webpayer, every time they want to see the latest values in the visualizations.So basically, they are closing the visualization and reopening it.
What is the query:
Users need not close and open the visualizations to see the latest values. The webplayer screen should automatically refresh in periodic intervals and show the latest values.It should be like a page reload in the browser in regular intervals.
Can anyone help me with this query?
Regards,
Kaka
Spotfire provides possibility to add the JavaScript to the dashboard so perhaps adding JavaScript that would reload the page at particular interval would be your bet here ?
Please check the link https://docs.tibco.com/pub/spotfire/6.0.0-november-2013/userguide-webhelp/text/text_javascript_example_scripts.htm.
We use the tx_news 2.3.0 (not the newest version! - right now not possible to update..) and there is a strange bug, that does not publish news when Publish Date is set (or better, it publish them days later).
As a work around I created a small script and run it with a cronjob:
UPDATE `tx_news_domain_model_news` SET `datetime` = `starttime`, `starttime` = 0 WHERE `starttime` <>0 and `starttime` < UNIX_TIMESTAMP()
Basicly it sets the Date & Time field = Publish Date and clears the Publish Date field if that is older then now. This workaround did a good job until we enabled some caches.
Now there is a problem that sometimes the new published article does not show up in the frontend in a news listview plugin. After Flush frontend caches it is there. But sometimes it works without clear the cache. And sometimes when not clearing the cache the article is there after some hours.
I do not want to disable the cache for the site with the news listview plugin on it.
So what would be the best way to handle this? Is there a way to only clear the cache for the tx_news plugin? Maybe even better only for a specific site or news folder? Maybe direct via the database?
Any ideas?
Edit: If I am right the cache should be deleted automaticly when you change something in the news article. As I do it via DB the cache is not deleted for this articles. So I tested it, I run the script, see that the articles are not published, go to backend, open onen one of this article and saved it (without any change), and after that all articles are published.
Maybe there is a way to simulate that?
I found a solution:
As I manipulate the database directly the cache system does not know about this change. So if you save an article after this change the cachesystem delete the entries for this site (and only for this site).
To force the cache to create a new cacheentry for this site I can manipulate the table cf_cache_pagesection and set the expires field to 1 (that means this cache entry is expired. I use the following SQl for it:
update `cf_cache_pagesection` set expires = 1 where identifier like '44_%'
(the page I want to change got the uid 44, that is used in the identifier)
Why it is sometime necessary to do Cache management to disable and Index management to re-index in magento.I am new in magento so if you know then reply this kindly.
In your development environment its advised to disable the cache because you tend to make the changes in the template / layout files often so to get it reflected on the frontend / website you are advised to disable the cache in your development environment. But don't do it in PRODUCTION.
And coming to Index Management, set it as "Save on Update" mode so that each time if you make some changes to your products, categories or attributes its getting re-indexed automatically and avoids the necessity to re-index it every time manually.
Specifically, "Block" data are the html blocks that the MVC generates to present to the frontend and even in the admin sometimes. Because of the caching and also session information, you need to log out of admin and back in for some changes to appear.
Depending on site volume, there might not be a penalty for turning off caching. If I'm doing a quick styling fix, I'll disable the block cache for a couple minutes.
I am working/maintaining an application built on Oracle ADF 11.1.1.4 version migrated from 10g during developement phase itself. We are using BC4j to talk to Oracle 10g database. The application is very heavily data centric and so there are chances that the query triggered through GUI may be have bad plan based on the search criteria entered by the user. Most of the places we have marked few fields mandatory to search on where potentially we see a bad query to be formed.
Issue: Currently in production user open muliple tabs for different screens, one of which is a screen where we have made it mandatory to enter few search values before searching/Querying the data. In the corresponding view criteria of that View Object we have marked those fields as selective required. But somehow we see a blind query triggered even when user hasn't clicked on search button on that page
It seems to comeup when the session expires on one of the pages opened and user clicks the OK. button
I am not sure is the framework triggereing some blind query when the page expires or else. There are many listeners on the page, but I am not sure why session timeeout can cause it.THe query is the same as that in the corresponding VO where we have maked few fields as selectively required. The long running query causes stuck thread on Weblogic server causing it to crash eventually after sometime.
Kindly anybody please advise if there has been an Oracle bug reported or any solution. We are seeing this on couple of pages where view criteria has few fields marked as selectively required.
Thanks
#Edit: The pages either jspx or page fragments jsff
You might be running into an effect as described here http://andrejusb.blogspot.ca/2012/08/adf-bc-passivationactivation-and-sql.html?m=1
You can try the technique I showed here https://tompeez.wordpress.com/2012/03/18/jdeveloper-preventing-return-of-large-row-sets-on-page-load-of-vo-using-bind-variable/ to prevent executing of queues on first load.