I am fine with replacing the defaultFs in our tests but have two comments:
1. Would be great to test Hive, HBase, Spark (any other?) before we
recommend to replace o3fs/ofs
2. Would be great to test o3fs and ofs with all the tests with the
same way (until o3fs is deleted).
Do we need to run tests with both defaultFs?
Marton
On 6/23/20 8:34 PM, Siyao Meng wrote:
Fellow Ozone developers,
I am thinking of making OFS the default since it should be the way
forward. The main reason I am sending this email is that I am about to do
some work to deprecate o3fs and replace existing o3fs paths in the existing
user guides with OFS ones. Also, new tests will be added to test OFS (e.g.
MapReduce acceptance tests). OFS follow-up work uber jira is created
at HDDS-3820.
At least for the upcoming 0.6.0 release, both o3fs and OFS will be usable
on the client. o3fs won't be gone any time soon.
If you have any concerns, comments and suggestions. Feel free to discuss
it in this thread. Thanks!
Cheers,
Siyao Meng
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
