DataSet API versus Stream API
Background
I posted a question earlier that had way too many parts, so I'm breaking out individual questions. Hopefully, these are easier to answer now and easier for other people to discover later. I can figure much of this out by testing myself, but am hoping others already know and can answer without much effort.
Question
Our likely cases are modestly sized data sets updated on a regular basis. These are not one-off data uploads, neither are they huge uploads. This leaves me wondering if we should be looking at the Stream API instead of the DataSet API. Stream sounds better for continuous and reliable updates, but also seems intended for high-volume pushes.
Any words of wisdom on when to pick one API over the other?
Also, can we define a DataSet via the DataSet API and then later use it with the Stream API? Not clear on that...it looks from the docs like the answer is "yes", and from other forum responses that the answer is "no." The examples show a Stream including a dataSet.id property, and then a full DataSet schema definition. I'm not clear how the two sets of functionality overlap. For example, if you open a Stream to an existing DataSet, do you have to provide a schema? What if it disagrees with the existing schema? I'd like to be able to set everything up with the DataSet API and then use the Stream API for pushes, where justified. If I need to maintain schema definitions on the client side for each push, that will be helpful to know in advance of designing and writing the code. If DataSet and Stream aren't interoperable, that will be very important to know in advance.
Thank you.
Comments
-
Hi,
Anyone help out with this request?Thanks,
0 -
Hey DataSquirrel,
Thank you for reaching out to Domo Support in regard to our Dataset/Stream API. I will get this over to my Connector team for added support on this compatibility, and the next available Technical Advisor will reach out to you with further steps and information.
If this is considered a high priority, then please call our number and reference the following ticket number:
Ticket: 05665910
1-801-805-9505
Have you been looking for a 1-stop shop for all your support cases? This message and all updates to this case can be tracked in the Customer Portal at support.domo.com. This portal makes it easy for you to track, update, and create all your support cases!
- Domo Technical Support
**Say “Thanks" by clicking the thumbs up in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0 -
@DataSquirrel
Here are the Knowledge Base articles on the Dataset API and Streams API. These will be your best resources on the topic. Outside of the details provided there, your advanced requests may most likely require help from your Client Success Manager as a consulting engagement.
https://developer.domo.com/docs/dataset/overview-50
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 298 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 729 Beast Mode
- 54 App Studio
- 40 Variables
- 680 Automate
- 175 Apps
- 451 APIs & Domo Developer
- 46 Workflows
- 8 DomoAI
- 34 Predict
- 14 Jupyter Workspaces
- 20 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 121 Manage
- 118 Governance & Security
- Domo Community Gallery
- 33 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive