Spotfire Ideas Portal
ADD A NEW IDEA

caching

Showing 20 of 4770

Incorporate TIBCO PSG Cache Framework into product

The TIBCO PSG Cache Framework is an API-driven mechanism to assist the developer in simplifying the steps to create single, multi-table and incremental cache tables by providing a minimal set of input values. For all cache types, a project profile...
almost 2 years ago in Spotfire Data Virtualization / caching 0 Future Consideration

Clean up used BCP cache tmp files during the process instead of at the end

Consider SQL Server or Hyperscale SQL DB or any derivative thereof. Consider a source table(s) with 100 million+ rows that will be cached into a target SQL Server database and use BCP to perform the load operation. Consider that the disk TDV is in...
almost 2 years ago in Spotfire Data Virtualization / caching 0 Future Consideration

Add primary keys to the cache management table DDL generation in TDV Studio

Customer: Qualcomm This idea is important for the team as they are using MYSQL data source as the cache target that was enabled for "Group replication" - in this scenario, any insert statements that were being run by TDV for cache refresh which in...
about 2 years ago in Spotfire Data Virtualization / caching 0 To be Reviewed

Add No cache refresh option to select

If you run a select on a cached table, and the cache is empty, the cache will automatically start to refresh. Sometimes you don't want that, as you only want the cache to refresh in tandem with other tables, or only at given times, while there may...
over 2 years ago in Spotfire Data Virtualization / caching 0 To be Reviewed

Indexes are created when cache tables are created for singular tables.

Indexes are created when creating a cache table with multiple tables when an index label is assigned to the view when the cache table is created. However, when creating a cache table for a single table, the index is not created. There must be situ...
almost 3 years ago in Spotfire Data Virtualization / caching 1 Unlikely to implement

Add Columns for node, sessionID, and requestID to cache_status tables, and have background job that marks the cache as failed if the session closes

Currently the Cache status table only mark whether a cache has started, but when it get's stuck, there is no option other than to mark the record as either failed or completed, and then go on. There is no information that allows you to find the pr...
about 3 years ago in Spotfire Data Virtualization / caching 0 Future Consideration

Truncate cache buckets instead of delete

Currently buckets have all their records deleted, and then the new records are inserted. In the database this means 2 write operations, and is a major cause of index fragmentation. Most databases allow you to truncate the table, which is only an a...
about 3 years ago in Spotfire Data Virtualization / caching 1 Planning to implement

More visible Destroy Cache button

One of the TDV customers requested that the Destroy Cache button be placed in a more visible position as shown in the attached image.
about 3 years ago in Spotfire Data Virtualization / caching 0 Unlikely to implement

Add the capability to disable the default cache to postgreSQL

Having this configuration available an admin will be able to permanently "disable" any caching to the local postgresSQL database which could be out of compliance for data sensitive systems.
over 4 years ago in Spotfire Data Virtualization / caching 0 Future Consideration

Drop created tables on cache destruction

Today when a TDV cache is destroyed, the underlying cache tables created in the database are orphaned. These tables need to be manually dropped by connecting to the database. TDV should execute drop commands to remove the cache tables when the ca...
almost 6 years ago in Spotfire Data Virtualization / caching 0 To be Reviewed
This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for Spotfire products and services. It is for informational purposes only and its contents are subject to change without notice. Planning to implement - generally 6-12 months out. Likely to Implement - generally means 12-18 months out. Copyright © 2014-2023 Cloud Software Group, Inc. All Rights Reserved. Cloud Software Group, Inc. ("Company") follows the EU Standard Contractual Clauses as per the Company's Data Processing Agreement. Terms of Use | Privacy Policy | Trademarks | Patents | Contact Us