TACHYON-198 Move UserConf usage to use TachyonConf

This PR consist next steps to integrate new configuration work:
-) Remove usage of UserConf
-) Push TachyonConf to Tachyon Hadoop's file system (aka TFS class).
-) Remove UserConf.java from repo.
Totally fine adding a new get method. Don't think there is a good reason to
keep merge though. When the use c case for it comes up, we can add it then.
Let's keep configs as small as possible for now
On Dec 13, 2014 11:25 AM, "Henry Saputra" <notifications@github.com> wrote:

> In core/src/main/java/tachyon/client/AbstractTachyonFS.java
> <https://github.com/amplab/tachyon/pull/564#discussion-diff-21790576>:
>
> > @@ -128,4 +136,12 @@ public synchronized boolean rename(int fileId, TachyonURI dstPath) throws IOExce
> >    public synchronized boolean rename(TachyonURI srcPath, TachyonURI dstPath) throws IOException {
> >      return rename(-1, srcPath, dstPath);
> >    }
> > +
> > +  /**
> > +   * Merge the {@link tachyon.conf.TachyonConf} instance
> > +   * @param tachyonConf
> > +   */
> > +  public synchronized void mergeConf(TachyonConf tachyonConf) {
>
> Ah I remember now why I did it that way.
> TachyonFS.get is a public interface which either we change the signature
> that could make code no longer backward compatible =(
> My suggestion is to add another Tachyon.get that takes TachyonConf and
> keep the "mergeConf" for now to merge the TachyonConf from caller; or
> expose access to TachyonFS.mTachyonConf as public accessor?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/amplab/tachyon/pull/564/files#r21790576>.
>