Data360 Analyze

Welcome to the Data360 Analyze community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Here are some useful links where you can find more information:

Product Announcements  Product Documentation  Ideas Portal

Discussions

Members

Resources

Events

 View Only

  • 1.  Can't rename a node, generates error message

    Posted 06-17-2017 18:53

    UPDATE: 

    This is a new user error, not a Dataverse error.  I created my first dataflow on server while logged in as admin and made it public.  When I came back to it later I logged in as rob.  

    It seems the purpose of public is just so others can run a job, but not make edits?  I thought it was intended for collaboration, but must be mistaken.  I saved a copy from Public to My and it's working fine.  

    Thanks, Rob

     

    - - - 

    Hi, 

    Just got Server up and running.  Am building my first job on Server:

    • Dataverse v3.1.2.1930
    • © 2017 Lavastorm Analytics, Inc. All rights reserved.
    • Client:Chrome v57.0.2987 (Windows 10)
    • Server:Apache Tomcat/8.5.11 (Linux)

    I created a JDBC node that successfully queried and wrote to a text file.  All looked good until I tried to rename the JDBC node.  Whether I click away or press enter to save the new node name, the job crashes.  I've closed out and retried and it keeps happening.  My changes don't save (any changes, I tried changing the JDBC job params too, but can't save.  Produces the message below.  **Please release the annotation feature (that I've seen in demos but was disappointed to learn isn't in the actual product) and I'll  never rename a node again, I swear.  Thanks, Rob

    Sorry, something has gone wrong

    An unexpected problem has caused the application to stop working properly.

    Failed to convert value of type [java.lang.String] to required type [com.lavastorm.lae.framework.core.model.ObjectResourceLocator]; nested exception is org.springframework.core.convert.ConversionFailedException: Failed to convert from type [java.lang.String] to type [@com.wordnik.swagger.annotations.ApiParam @org.springframework.web.bind.annotation.PathVariable com.lavastorm.lae.framework.core.model.ObjectResourceLocator] for value 'default'; nested exception is com.lavastorm.logging.LoggableRuntimeException: The URI scheme 'null' is not a valid scheme for a Dataverse resource.

     

     



  • 2.  RE: Can't rename a node, generates error message

    Posted 06-19-2017 15:03

    Dear Robert,

    I'm sorry to hear that you are struggling to share data flows.  Using a pre-release version of the Dataverse 3.1.3 server, two of our engineers edited public data flows created by the admin user.  This implies that this issue may be isolated to 3.1.2.

    As for restricting users to only running data flows, let me check with our Engineering team to get the full picture.

    The 3.1.3 release of Dataverse should be available any day.

    Hope that helps,

    Rocco

     



  • 3.  RE: Can't rename a node, generates error message

    Posted 06-21-2017 09:35

    Dear Rob,

    To answer your questions about the functionality of the "My Documents" folder versus the "Public Documents" folder, the idea most certainly is collaboration.  However, the collaboration is focused around data flow designers.  Therefore, other users with the "End User" role can edit anything in the Public Documents folder.

    In 3.1.4, there will be a new user role called Explorer in which users can see and run data flows without being able to make changes.  My understanding is that this role applies to all data flows that are shared with this user.  3.1.4 should be out in the next month or so.

    Later in Q3, Dataverse users will be able to group data flows into folders in order to limit access to only certain users.  This may also help with the situation you describe.

    Feel free to write back if you have any additional questions.

    Rocco