Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Hi Robert,As part of our documentation we are working on sharing limits and quotas of CDF services before summer. Hopefully this will resolve your particular query in this context.Best,Shakya
Dear Robert,It would be great if we discussed the intricacies of the model versioning here a bit more. In general, what is in our roadmap for 2023 and beyond is the ability of users to view older version of data model and its data. Currently, this is in design phase and hoping for opportunities in future for some additional feedback gathering from critical end-users. Let us touchbase in the triweekly meeting tomorrow to get those insights locked. Thanks!
Hi Robert, thanks for providing the detailed request and relevant initiative from Statnett end.We are happy to share that this general graph traversal user workflows are being developed to provide End to end UI Experience enabled on top of through Flexible Data Modelling development and is now in product planning.We will make sure to loop you in to define the specifics and capture the feedback on time. As a developer, I want to explore the datamodel in CDF, so that I can verify my integration and understand and traverse the datamodel. Front-end and back-end developers are both dependent on visually exploring the datamodel in CDF. The current tooling in Fusion is lacking in two major regards: a) Traversing instances in the graph one gets easily lost in Fusion. Having a Graph-exploration tool allows for managing traversals in a relational datamodel for quickly creating and iterating on Applications. b) Traversing a meta-graph (graph describing the relations between different resources
Hi Robert, thanks for providing the detailed request and relevant initiative from Statnett endWe are excited to share that this general improvements in Search and Filter user workflows are captured through Flexible Data Modelling development in product planning. In short, User is able to query data in Fusion UI and in their respective apps. They should be able to do basic search, filtering and aggregation queries while also enabled to be able to create data models with properties, types, relationships that will be queryable through GraphQL. Subsequently, extract and retain information about the connections between objects to create advanced solutions/outputs through the relevant APIs - making full use of the process-centricity in a data modelling context. As a developer, I want to search for resources, so that the SME can access relevant equipments. The current search functionality in CDF is at a bare minimum, and getting the SME to the correct equipment is cumbersome and requires sig
Hi Robert, thanks for providing the detailed request and relevant initiative from Statnett end.Understanding the criticality - we have captured this into our planning and will soon share details about the plans. Let us connect a bit more to strip down this capability need into concrete functions that should be enabled by CDF, work towards a success definition. As a developer, I want to use a Streaming data connector in the data integration, so that the data pipeline codebase can be reduced in complexity. Extracting data from a Stream prorcess to CDF RAW/CLEAN is a critical piece of infrastructure maintained at Statnett. The same features as exists for SQL extraction would allow us to reduce complexity and increase maintainability of the extraction process. This code must be executable on-prem at Statnett.
Hi Robert, thanks for providing the detailed request and relevant initiative from Statnett endWe are excited to share that this particular user workflow is captured in our product planning. In short, we will enable end-users to be able to create data models with properties, types, relationships that will be queryable through GraphQL. Subsequently, extract and retain information about the connections between objects to create advanced solutions/outputs through the relevant APIs - making full use of the process-centricity in a data modelling context. This request relates to As a developer I want to make queries on the datamodel that retain information about the connections between objects. Making large queries on the graph connected by Relationships requires the client-side to re-construct the graph in memory. There are no semantics in CDF for preserving ordering in relationship queries, or imputation for order preservation. Meaning that for each step in the graph when making paral
EDIT: SQL is out of scope for 2022 as well.
Short responses:Querying into the data model supported with GraphQL - SQL would be an upcoming feature in 2022 through the Flexible Data Model initiative. Please note interaction with REST will be out-of-scope for this year. However, graph traversal capabilities - though part of product plan (2023 and beyond) would require further product discovery (especially to establish the developer or end-user workflow design). As a developer, I want to make verbose queries on Assets, so that I have to maintain less complex code on the client side of applications. Retrieving Assets by Relationships and the Hierarchy is cumbersome and divests complexity to the client. A verbose query language for the datamodel (like SQL or SPARQL, GraphQL formats allow) would delegate complexity back to the server, and is preferable to the in-memory re-building of the model that now takes place. We understand that most of this feature will be covered by Flexible Data Models, but we’re curious about the graph-trave
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.