[ https://issues.apache.org/jira/browse/BIGTOP-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233479#comment-14233479 ]
jay vyas commented on BIGTOP-1493: ---------------------------------- Okay, for now we can re roll the patch to ditch mapreduce tests, and simply confirm - {{tachyon fs ls}} {{tachyon fs put}} etc works , and that the under fs (local, hdfs, whatever) is able to persist things properly. - {{hadoop fs -ls tachyon:///blah}} should also work properly (this will confirm that the core-site.xml is configured in a system, which is a good test to run i think. > Add smoke test for tachyon > -------------------------- > > Key: BIGTOP-1493 > URL: https://issues.apache.org/jira/browse/BIGTOP-1493 > Project: Bigtop > Issue Type: Test > Components: tests > Affects Versions: 0.8.0 > Reporter: jay vyas > Assignee: David Capwell > Attachments: BIGTOP-1493.1.patch, BIGTOP-1493.2.patch, > BIGTOP-1493.3.patch, iTest-deps.png > > > Tachyon as an in memory cache will be emerging as a common feature in hadoop > and spark based clusters. > Lets create a smoke test under the {{smoke-tests}} which uses the > {{tachyon:///}} url. > To get started with the smoke tests, you can > 1) Run the vagrant recipe under bigtop-deploy/vm/vagrant-puppet . This will > demonstrate the way you spin up a bigtop based hadoop cluster. > 2) Now, you can do {{vagrant ssh}} into your cluster, and simply edit the > smoke tests or install stuff. Re running the smoke-tests.sh file should test > that your new tests work . At that point, just exit your VM, and commit your > changes and submit the new patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)