s3

Hi. First of all, kudos to you for the VFS cache - it's really brilliant. I have one request though.

For a little background, as of now I'm using the following settings:

--vfs-cache-mode full \
  --vfs-cache-max-size 500G \
  --vfs-cache-max-age 5000h \
  --vfs-cache-poll-interval 5m \
  --vfs-read-ahead 2G \
  --bwlimit-file 32M \
  --vfs-read-chunk-size=64M \
  --vfs-read-chunk-s

With Sidecar now changing its readiness status depending on whether it can establish a connection with Prometheus, there is spam of:

{"caller":"intrumentation.go:48","level":"info","msg":"changing probe status","status":"ready","ts":"2022-01-06T16:37:27.595400008Z"}

We shouldn't print this message if the status is set to the same value as the previous one.

What went wrong?

I'm getting deprecation warnings with openSSL encryption.

[2019/09/05 08:38:52][info] Using Encryptor::OpenSSL to encrypt the archive.
[2019/09/05 08:40:22][warn] Pipeline STDERR Messages:
[2019/09/05 08:40:22][warn] (Note: may be interleaved if multiple commands returned error messages)
[2019/09/05 08:40:22][warn]
[2019/09/05 08:40:22][warn] *** WARNING : depre

Problem description

Hi, smart_open currently supports hdfs://, viewfs:// is also a hadoop file system which is similar to hdfs://.

I find that tf.io.gfile.GFile of tensorflow can support both hdfs:// and viewfs://, is it possible that smart_open add support for viewfs://?

Thanks~