No, but that’s a good idea. Not sure if PDF format can be streamed/processed parallely.
I thought, if you would bind FUSE to expose Ignite’s file system, I would leave an API for the developer, to let him expose the data in Ignite. Since it’s a user-space file system, we can expose directories/files as we want. I see that as useful, as one can later mount the file system via smb/cifs to other platforms and have access to in-memory real time system with reports etc… Something similar that Alfresco is doing with JLan. I might be wrong :) > On May 5, 2015, at 4:12 AM, Dmitriy Setrakyan <[email protected]> wrote: > > On Mon, May 4, 2015 at 7:08 PM, Marko Jevtic <[email protected]> wrote: > >> Sorry for dropping like this in the topic :) >> >> But I think it would be extremely useful if we Ignite would provide an API >> to virtually expose structures in cache. >> Like computing on fly (on access) csv/excel files or pdf reports from >> cache, besides the regular usage to access Ignite’s file system. >> > > Hm... Are you suggesting parallel processing of different sections of PDF > files from different compute jobs, or have a single compute job process the > whole file? > > >> >> Just an idea. >> >>> On May 5, 2015, at 3:58 AM, Dmitriy Setrakyan <[email protected]> >> wrote: >>> >>> I have noticed a Jira filed to make IGFS mountable: >>> https://issues.apache.org/jira/browse/IGNITE-854 >>> >>> The integration proposed is via Fuse framework which would allow us mount >>> IGFS just like a regular Linux file system. >>> >>> This seems like a pretty big undertaking. Even though it sounds pretty >> cool >>> in theory, it would be interesting to find out form the community if >>> everyone else finds it useful and maybe suggest some potential use cases >>> for it. >>> >>> Also, seems like Fuse framework is not being actively developed. Last >>> release came out in July, 2013. How safe is it to use this framework? >>> >>> D. >> >>
