GitHub user cloverhearts opened a pull request:
https://github.com/apache/zeppelin/pull/1929
[ZEPPELIN-1997] Added derbylog in .gitignore
### What is this PR for?
Added derbylog in .gitignore
Sometime created derby.log in bin directory.
We should stop tracking derbylog
derby.log
```
1 ----------------------------------------------------------------
2 Thu Jan 19 23:45:08 PST 2017:
3 Booting Derby version The Apache Software Foundation - Apache Derby -
10.10.2.0 - (1582446): instance a816c00e-0159-bad6-0f44-000030e6b528
4 on database directory
/Users/cloverhearts/Source/nflabs/zeppelin/bin/metastore_db with class loader
org.apache.spark.sql.hive.client.IsolatedClientLoader$$anon$1@74101877
5 Loaded from
file:/Users/cloverhearts/Source/nflabs/zeppelin/interpreter/spark/dep/zeppelin-spark-dependencies_2.10-0.7.0-SNAPSHOT.jar
6 java.vendor=Oracle Corporation
7 java.runtime.version=1.8.0_101-b13
8 user.dir=/Users/cloverhearts/Source/nflabs/zeppelin/bin
9 os.name=Mac OS X
10 os.arch=x86_64
11 os.version=10.12.2
12 derby.system.home=null
13 Database Class Loader started - derby.database.classpath=''
```
### What type of PR is it?
Improvement
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1997
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloverhearts/zeppelin ZEPPELIN-DERBYLOG
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1929.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1929
----
commit e4765c9a79efc1dc60c23bdea624dcaf631b24b8
Author: cloverhearts <cloverhearts...@gmail.com>
Date: 2017-01-21T13:59:21Z
added bin/derby.log in .gitignore
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
