Spotfire Ideas Portal
ADD A NEW IDEA

caching

Showing 21 of 4760

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...
over 2 years ago in TIBCO Data Virtualization / caching 1 Planning to implement

Cache job auto-restart upon failure

We would like the option to automatically reattempt a cache job when it fails. We have some public api data sources that randomly fail from time to time, and they succeed if you just restart them. It would save us time and failure alerts if they c...
over 5 years ago in TIBCO Data Virtualization / caching / data movement 2 Future Consideration

Ability to kill running caching jobs that are stuck or have been running for very long

Admin should have a kill button on caching jobs that are running for too long or are stuck due to some reasons. As now we have to manually create a procedure to change the status from active to failed but this functionality should be included in t...
about 7 years ago in TIBCO Data Virtualization / caching 2 Planning 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...
over 2 years ago in TIBCO 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...
over 5 years ago in TIBCO Data Virtualization / caching 0 To be Reviewed

Provide an option to setup a custom database for the default cache db

The DV server currently uses an embedded PostgreSQL database as the default cache. This enhancement would allow the developer or admin the ability configure any supported cache data source as their "default" cache.
over 7 years ago in TIBCO Data Virtualization / caching 0 Future Consideration

Deploy only cache tables that are dependents of selected services instead of all tables in the cache database

Currently when deploying objects and selecting dependencies cache databases are treated differently than other data sources. With standard data sources only tables in the lineage of the selected objects are included in the car file. For caching, e...
over 6 years ago in TIBCO Data Virtualization / caching 1 Future Consideration

Allow customization of the CREATE TABLE DDL for cache creation

Allow a developer to customize the CREATE TABLE DDL when creating cache tables so that specific clauses for logging, distributed by, tpartitioning or storage parameters can be added to the CREATE statement. This could be handed edited by the devel...
over 7 years ago in TIBCO Data Virtualization / caching 1 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...
over 1 year ago in TIBCO 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...
almost 2 years ago in TIBCO 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