Hey, And is it required to have a file system APIs enabled? If not, you can deploy Ignite in a standard configuration (cache, data grid or IMDB) and use key-val, SQL, etc. for data access.
- Denis On Wed, May 15, 2019 at 10:27 AM Chris Software <softwarechri...@gmail.com> wrote: > Hello! > > We are using it as a standalone, in order to create a distributed file > system for a (hopefully) fast cache of a few hours of data. We are not > using it in front of Hadoop, although there is some discussion of > eventually backing it with Cassandra, should we decide to keep more than a > few hours of data in the future. > > Chris > > On Tue, May 14, 2019 at 10:35 PM Denis Magda <dma...@apache.org> wrote: > >> Hello, >> >> Are you using IGFS as a standalone file system or as a way to accelerate >> Hadoop? If for the latter then I would suggest considering an alternate >> solution that is proved to be efficient for production deployment and >> Hadoop offloading: >> >> http://apache-ignite-users.70518.x6.nabble.com/SW-recommendation-Ignite-Native-Persistence-for-traditional-relational-data-warehouse-td28135.html >> >> - >> Denis >> >> >> On Tue, May 14, 2019 at 12:26 PM Chris Software < >> softwarechri...@gmail.com> wrote: >> >>> Hello, >>> >>> I am wondering what sort of File Properties can be set in ignite using >>> the IgniteFileSystem.create(IgfsPath path, int bufSize, boolean overwrite, >>> int replication, long, blockSize, Map<String, String> props) method. >>> >>> I am using the default storage. It's not obvious to me in the code what >>> choices I have for this properties file. I don't see it documented in the >>> javadoc. >>> >>> Thank you. >>> >>
