Does not have any direct IO.Error type associated with it since missing functions should be considered as IO.Error.Fatal and should be resolved otherwise compaction will fail and pause for that Segment and will only continue ones this function is available in function store.
Does not have any direct IO.Error type associated with it since missing functions should be considered as IO.Error.Fatal and should be resolved otherwise compaction will fail and pause for that Segment and will only continue ones this function is available in function store.
functionID itself is not logged or printed to console since it may contain sensitive data but instead this Exception with the functionID is returned to the client for reads and the exception's string message is only logged.
the id of the missing function.
(Since version ) see corresponding Javadoc for more information.
Exception types for all known IO.Errors that can occur. Each IO.Error can be converted to Exception which which can then be converted back to IO.Error.
SwayDB's code itself does not use these exception it uses IO.Error type. These types are handy when converting an IO type to scala.util.Try by the client using IO.toTry.