Hi, David raises an interesting point regarding the consequences of using undocumented features.
I for one feel that not having easy and direct access to system-level resources such as the filesystem [1] for those occasions where I need them makes it more difficult to build "pure" MarkLogic-based applications using its one-in-all appserver approach. At the end of the day (and still with the idea in mind of wanting to create an application without other dependencies), isn't it a bit overkill to have to call a service that is PHP, node.js or Java-based to do something as basic as deleting a file or directory? If one wants to align with these technology stacks (and the inclusion of the V8 Javascript engine in the next version of MarkLogic may hint that way), then direct and efficient access to these system-level resources appears mandatory. So I would actually argue in favour of making these functions documented and supported. :-) Just my two cents. cheers, Jakob. [1] Caveat: I don't know how feasible this is in a MarkLogic cluster environment. On Tue, May 13, 2014 at 8:37 PM, David Ennis <[email protected]> wrote: > And, of course, as far as sharp tools are concerned, coming from the linux > world, there is a great combination: > > xdmp:save > named pipes > a few lines of shell script in a loop including cat, sed and eval > > I use this myself to gain access to the system (with some constraints in > place for safety, of course - so a real-life situation is a bit more than a > few lines..), but it is a neat approach that works. I might write > something up about it. > > Regards, > David > > > On 13 May 2014 20:24, David Ennis <[email protected]> wrote: > >> HI. >> >> There are a handful of features/functions that are undocumented. I also >> have a use for these two functions. >> >> However, even knowing that they are there I will refrain from using them >> for the simple fact that if a feature is not in the official documents, >> then it is not officially supported. If it is not officially supported, >> then it is always subject to change/deletion without notice. >> >> The deletion (like other system-related tasks) can be accomplished with >> some elbow-grease by calling another service or writing a config file of >> some sort that will be picked up. >> >> Regards, >> David Ennis >> >> >> On 13 May 2014 16:37, Jakob Fix <[email protected]> wrote: >> >>> Oops, I think we got this information following discussion on the EA7 >>> forum last year (together with the sharp tool caveat). >>> >>> cheers, >>> Jakob. >>> >>> >>> On Tue, May 13, 2014 at 4:16 PM, Florent Georges <[email protected]>wrote: >>> >>>> Thank you, Jakob. That does exactly what I was looking for (but >>>> how do you do to be aware of those functions?) >>>> >>>> Yes I know this is a sharp tool (I don't use it without asking a >>>> confirmation to the user first, with the full path being displayed). If >>>> someone comes here in the archives, if you want more context and/or more >>>> warnings about using this: >>>> http://marklogic.markmail.org/thread/46pyr3xrkuqncab5. >>>> >>>> Regards, >>>> >>>> -- >>>> Florent Georges >>>> http://fgeorges.org/ >>>> http://h2oconsulting.be/ >>>> >>>> Jakob Fix wrote: >>>> >>>> Hi Florent, >>>> >>>> there is an undocumented xdmp:filesystem-directory-delete( dirname as >>>> xs:string ) function. >>>> same for files: xdmp:filesystem-file-delete( filename as xs:string). >>>> sharp tools, as they say. >>>> >>>> cheers, >>>> Jakob. >>>> >>>> >>>> On Mon, May 12, 2014 at 8:41 PM, Florent Georges <[email protected]>wrote: >>>> >>>> Hi, >>>> >>>> Has there any way to delete a directory been added to MarkLogic 7.0? >>>> I create directories and files on the file system from an application in >>>> MarkLogic. I would like to delete some of them from within the >>>> application. >>>> >>>> I know that it was not possible back in September 2012, has it been >>>> added since then? >>>> >>>> Regards, >>>> >>>> -- >>>> Florent Georges >>>> http://fgeorges.org/ >>>> http://h2oconsulting.be/ >>>> >>>> >>>> >>>> _______________________________________________ >>>> General mailing list >>>> [email protected] >>>> http://developer.marklogic.com/mailman/listinfo/general >>>> >>>> >>>> >>>> >>>> >>> >>> _______________________________________________ >>> General mailing list >>> [email protected] >>> http://developer.marklogic.com/mailman/listinfo/general >>> >>> >> > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > >
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
