ignite-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sboi...@apache.org
Subject [21/37] incubator-ignite git commit: # sprint-1 Updated readme files under docs folder.
Date Thu, 29 Jan 2015 08:48:49 GMT
# sprint-1 Updated readme files under docs folder.


Project: http://git-wip-us.apache.org/repos/asf/incubator-ignite/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-ignite/commit/f5d64b2e
Tree: http://git-wip-us.apache.org/repos/asf/incubator-ignite/tree/f5d64b2e
Diff: http://git-wip-us.apache.org/repos/asf/incubator-ignite/diff/f5d64b2e

Branch: refs/heads/ignite-113
Commit: f5d64b2e1fe87d6d81d7b9eb532ba6776200dd91
Parents: 2286097
Author: Dmitiry Setrakyan <dsetrakyan@gridgain.com>
Authored: Thu Jan 29 06:30:57 2015 +0000
Committer: Dmitiry Setrakyan <dsetrakyan@gridgain.com>
Committed: Thu Jan 29 06:31:15 2015 +0000

----------------------------------------------------------------------
 docs/core-site.gridgain.xml   |  89 ----------------------
 docs/core-site.ignite.xml     |  89 ++++++++++++++++++++++
 docs/gridgain_readme.md       | 149 -------------------------------------
 docs/gridgain_readme.pdf      | Bin 407698 -> 0 bytes
 docs/hadoop_readme.md         |  80 +++++++-------------
 docs/hadoop_readme.pdf        | Bin 411788 -> 82297 bytes
 docs/hive-site.gridgain.xml   |  36 ---------
 docs/hive-site.ignite.xml     |  36 +++++++++
 docs/mapred-site.gridgain.xml |  79 --------------------
 docs/mapred-site.ignite.xml   |  79 ++++++++++++++++++++
 10 files changed, 230 insertions(+), 407 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/f5d64b2e/docs/core-site.gridgain.xml
----------------------------------------------------------------------
diff --git a/docs/core-site.gridgain.xml b/docs/core-site.gridgain.xml
deleted file mode 100644
index 0054b60..0000000
--- a/docs/core-site.gridgain.xml
+++ /dev/null
@@ -1,89 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
-<!--
-  Licensed to the Apache Software Foundation (ASF) under one or more
-  contributor license agreements.  See the NOTICE file distributed with
-  this work for additional information regarding copyright ownership.
-  The ASF licenses this file to You under the Apache License, Version 2.0
-  (the "License"); you may not use this file except in compliance with
-  the License.  You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing, software
-  distributed under the License is distributed on an "AS IS" BASIS,
-  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-  See the License for the specific language governing permissions and
-  limitations under the License.
-  -->
-
-<!--
-    This template file contains settings needed to run Apache Hadoop jobs
-    with GridGain's distributed in-memory file system GGFS.
-
-    You can replace '$HADOOP_HOME/etc/hadoop/core-site.xml' file with this one
-    to work with GridGain GGFS nodes running on localhost (these local nodes can be
-    a part of distributed cluster though). To work with file system on remote
-    hosts you need to change the host of file system URI to any host running
-    GridGain's GGFS node.
-
-    Note that GridGain jars must be in Apache Hadoop client classpath to work
-    with this configuration.
-
-    Run script '$GRIDGAIN_HOME/bin/setup-hadoop.{sh|bat}' for Apache Hadoop client setup.
--->
-
-<configuration>
-    <!--
-        Set default file system to GGFS instance named "ggfs" configured in GridGain.
-    -->
-    <property>
-        <name>fs.default.name</name>
-        <value>ggfs://ggfs@localhost</value>
-    </property>
-
-    <!--
-        Set Hadoop 1.* file system implementation class for GGFS.
-    -->
-    <property>
-        <name>fs.ggfs.impl</name>
-        <value>org.apache.ignite.fs.hadoop.v1.GridGgfsHadoopFileSystem</value>
-    </property>
-
-    <!--
-        Set Hadoop 2.* file system implementation class for GGFS.
-    -->
-    <property>
-        <name>fs.AbstractFileSystem.ggfs.impl</name>
-        <value>org.apache.ignite.fs.hadoop.v2.GridGgfsHadoopFileSystem</value>
-    </property>
-
-    <!--
-        Disallow data node replacement since it does not make sense for GridGain's GGFS nodes.
-    -->
-    <property>
-        <name>dfs.client.block.write.replace-datanode-on-failure.policy</name>
-        <value>NEVER</value>
-    </property>
-
-    <!--
-        Allow to write the job statistics into GGFS.
-    -->
-    <!--
-    <property>
-        <name>gridgain.counters.writer</name>
-        <value>org.apache.ignite.internal.processors.hadoop.counter.GridHadoopFSCounterWriter</value>
-    </property>
-    -->
-
-    <!--
-        By default data is placed into the file /user/<user_name>/<job_id>/performance
-        You can override this path with using macro ${USER} that is to injection of submitter
user name.
-    -->
-    <!--
-    <property>
-        <name>gridgain.counters.fswriter.directory</name>
-        <value>/user/${USER}</value>
-    </property>
-    -->
-</configuration>

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/f5d64b2e/docs/core-site.ignite.xml
----------------------------------------------------------------------
diff --git a/docs/core-site.ignite.xml b/docs/core-site.ignite.xml
new file mode 100644
index 0000000..0054b60
--- /dev/null
+++ b/docs/core-site.ignite.xml
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+  -->
+
+<!--
+    This template file contains settings needed to run Apache Hadoop jobs
+    with GridGain's distributed in-memory file system GGFS.
+
+    You can replace '$HADOOP_HOME/etc/hadoop/core-site.xml' file with this one
+    to work with GridGain GGFS nodes running on localhost (these local nodes can be
+    a part of distributed cluster though). To work with file system on remote
+    hosts you need to change the host of file system URI to any host running
+    GridGain's GGFS node.
+
+    Note that GridGain jars must be in Apache Hadoop client classpath to work
+    with this configuration.
+
+    Run script '$GRIDGAIN_HOME/bin/setup-hadoop.{sh|bat}' for Apache Hadoop client setup.
+-->
+
+<configuration>
+    <!--
+        Set default file system to GGFS instance named "ggfs" configured in GridGain.
+    -->
+    <property>
+        <name>fs.default.name</name>
+        <value>ggfs://ggfs@localhost</value>
+    </property>
+
+    <!--
+        Set Hadoop 1.* file system implementation class for GGFS.
+    -->
+    <property>
+        <name>fs.ggfs.impl</name>
+        <value>org.apache.ignite.fs.hadoop.v1.GridGgfsHadoopFileSystem</value>
+    </property>
+
+    <!--
+        Set Hadoop 2.* file system implementation class for GGFS.
+    -->
+    <property>
+        <name>fs.AbstractFileSystem.ggfs.impl</name>
+        <value>org.apache.ignite.fs.hadoop.v2.GridGgfsHadoopFileSystem</value>
+    </property>
+
+    <!--
+        Disallow data node replacement since it does not make sense for GridGain's GGFS nodes.
+    -->
+    <property>
+        <name>dfs.client.block.write.replace-datanode-on-failure.policy</name>
+        <value>NEVER</value>
+    </property>
+
+    <!--
+        Allow to write the job statistics into GGFS.
+    -->
+    <!--
+    <property>
+        <name>gridgain.counters.writer</name>
+        <value>org.apache.ignite.internal.processors.hadoop.counter.GridHadoopFSCounterWriter</value>
+    </property>
+    -->
+
+    <!--
+        By default data is placed into the file /user/<user_name>/<job_id>/performance
+        You can override this path with using macro ${USER} that is to injection of submitter
user name.
+    -->
+    <!--
+    <property>
+        <name>gridgain.counters.fswriter.directory</name>
+        <value>/user/${USER}</value>
+    </property>
+    -->
+</configuration>

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/f5d64b2e/docs/gridgain_readme.md
----------------------------------------------------------------------
diff --git a/docs/gridgain_readme.md b/docs/gridgain_readme.md
deleted file mode 100644
index 2bd7370..0000000
--- a/docs/gridgain_readme.md
+++ /dev/null
@@ -1,149 +0,0 @@
-<center>
-![GridGain Logo](http://www.gridgain.com/images/logo/logo_mid.png "GridGain Logo")
-</center>
-
-<div style="height: 5px"></div>
-
-## 1. GridGain In-Memory Data Fabric
-
-GridGain’s In-Memory Data Fabric is designed to deliver uncompromised performance for the
widest array of in-memory computing use cases.
-
-Following components are included in the fabric:
-* `In-Memory High Performance Computing (HPC)` - includes distributed clustering, messaging,
events, and computational features.
-* `In-Memory Data Grid` - partitioned in-memory key-value store with support for ACID transactions,
off-heap memory, SQL, and more.
-* `In-Memory Streaming` - supports event workflow, rolling data windows and indexing, continuous
querying, and more.
-
-Enterprise Features:
-* Portable Objects
-* Dynamic data structure changes without restarting cluster
-* Cross-language support, including Java (JVM), .NET (C#), C++
-* Datacenter replication
-* Rolling production updates
-* Local recoverable store
-* Network segmentation protection
-* Secure authentication and Secure client sessions
-* GUI Management & Monitoring
-
-## 2. GridGain Installation
-GridGain distribution comes in a ZIP file that simply needs to be unzipped, and `GRIDGAIN_HOME`
environment variable
-can optionally be set to point to it.
-
-There are no additional steps required for GridGain installation in such multi machine setup.
-
-Installation requirements:
-
-1. Windows, Linux, or MacOS environment.
-2. Java 7 or 8 (latest update is advisable).
-3. Point `JAVA_HOME` environment variable to your JDK or JRE installation.
-4. Optional: point `GRIDGAIN_HOME` environment variable to the GridGain installation folder.
-
-### 2.1 Check GridGain Installation
-
-To verify GridGain installation, you can execute the GridGain startup script.
-
-The following command will startup GridGain with default configuration using Multicast node
discovery.
-
-    bin/ggstart.{sh|bat}
-
-The following command will startup GridGain with example configuration.
-
-    bin/ggstart.{sh|bat} examples/config/example-compute.xml
-
-If GridGain was installed successfully, the output from above commands should produce no
exceptions or errors.
-Note that you may see some warnings during startup, but this is OK as they are meant to inform
that certain
-functionality is turned on or off by default.
-
-You can execute the above commands multiple times on the same machine and make sure that
nodes discover each other.
-Here is an example of log printout when 2 nodes join topology:
-
-    ... Topology snapshot [nodes=2, CPUs=8, hash=0xD551B245]
-
-You can also start GridGain Management Console, called Visor, and observe started nodes show
up on Visor Dashboard.
-To startup Visor, you should execute the following script:
-
-    /bin/ggvisorcmd.{sh|bat} (Command-line, available in open source)
-    /bin/ggvisorui.{sh|bat} (GUI mode, enterprise version only)
-
-### 2.2 Running GridGain Examples
-
-GridGain comes with many well documented examples. All examples have documentation about
how they should be
-started and what the expected outcome should be.
-
-> Use provided pom.xml to import examples into IDE of your choice.
-
-## 3. Maven
-GridGain provides repository for its Maven artifacts.
-
-- GridGain Open Source repository is hosted at Maven Central (no additional URL required)
-- GridGain Enterprise repository is located at http://www.gridgainsystems.com/nexus/content/repositories/external
-
-### 3.1 Maven Artifacts
-GridGain Maven repository has `4` artifacts (add `'-ent'` for enterprise edition):
-
-* gridgain-hpc - contains jars and dependencies for In-Memory High Performance Computing
(HPC)
-* gridgain-datagrid - contains jars and dependencies for In-Memory Data Grid
-* gridgain-streaming - contains jars and dependencies for In-Memory Streaming
-* gridgain-fabric - contains jars and dependencies for all GridGain editions
-
-### 3.2 Maven Example
-
-#### 3.2.1 Open Source
-
-    <dependency>
-        <groupId>org.gridgain</groupId>
-        <artifactId>gridgain-fabric</artifactId>
-        <version>${ignite.version}</version>
-        <type>pom</type>
-    </dependency>
-
-#### 3.2.2 Enterprise
-
-    <repository>
-        <id>GridGain External Repository</id>
-        <url>http://www.gridgainsystems.com/nexus/content/repositories/external</url>
-    </repository>
-    ...
-    <dependency>
-        <groupId>org.gridgain</groupId>
-        <artifactId>gridgain-fabric-ent</artifactId>
-        <version>${ignite.version}</version>
-        <type>pom</type>
-    </dependency>
-
-## 4. Starting Grid Nodes
-Grid nodes can be started by executing `bin/ggstart.{sh|bat}` script and passing a relative
path to GridGain configuration file. If no file is passed, then grid nodes are started with
default configuration using Multicast discovery protocol.
-
-Here is an example of how to start GridGain node with non-default configuration:
-
-    `bin/ggstart.sh examples/config/example-cache.xml`
-
-## 5. Management & Monitoring with Visor
-GridGain comes with GUI and CLI (command) based DevOps Managements Consoles delivering advance
set of management and monitoring capabilities. Visor GUI is based on a standalone Java application
and CLI version is built on top of Scala REPL providing fully scriptable and customizable
DevOps environment.
-
-To start Visor GUI console (enterprise edition only), execute the following command:
-
-    `bin/ggvisorui.sh`
-
-To start Visor in console mode you should execute the following command:
-
-    `bin/ggvisorcmd.sh`
-
-On Windows, run the same commands with `.bat` extension.
-
-> **NOTE:** Visor GUI console has a much richer set of functionality over Visor command-based
console.
-> You should always prefer Visor GUI console whenever possible.
-
-Here is an example of `Visor Data Grid Tab` which provides overall view on data grid.
-
-<img width="800" src="http://www.gridgain.com/images/visor_database2.png">
-
-Here is an example of `Visor Cache Tab` which provides view on individual cache.
-
-<img width="800" src="http://www.gridgain.com/images/visor_cache.png">
-
-## 6. Scala Integration
-GridGain provides a very nice and easy to use DSL for Scala users called `Scalar`. If you
like Scala, take a look at
-Scalar examples located under `examples/src/main/scala` folder.
-
-## 7. Javadoc & Scaladoc
-All documentation is shipped with it and you can find it under `docs/javadoc` and `docs/scaladoc`
sub-folder respectively.

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/f5d64b2e/docs/gridgain_readme.pdf
----------------------------------------------------------------------
diff --git a/docs/gridgain_readme.pdf b/docs/gridgain_readme.pdf
deleted file mode 100644
index 0e36849..0000000
Binary files a/docs/gridgain_readme.pdf and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/f5d64b2e/docs/hadoop_readme.md
----------------------------------------------------------------------
diff --git a/docs/hadoop_readme.md b/docs/hadoop_readme.md
index 95a04ed..1fda55d 100644
--- a/docs/hadoop_readme.md
+++ b/docs/hadoop_readme.md
@@ -1,22 +1,22 @@
 <center>
-![GridGain Logo](http://www.gridgain.com/images/logo/logo_mid.png "GridGain Logo")
+![Ignite Logo](https://ignite.incubator.apache.org/images/logo3.png "Ignite Logo")
 </center>
 
-## 1. GridGain In-Memory Accelerator For Apache Hadoop
+## 1. Apache Ignite In-Memory Accelerator For Apache Hadoop
 
-GridGain’s In-Memory Accelerator For Apache Hadoop is designed to deliver uncompromised
performance for existing Apache 
+Ignite In-Memory Accelerator For Apache Hadoop is designed to deliver uncompromised performance
for existing Apache 
 Hadoop 2.2 or above applications with zero code change as well as simplicity of installation
and configuration across all the 
 supported platforms. 
 
 ## 2. Installation
 
-GridGain distribution comes in a ZIP file that simply needs to be unzipped. The Accelerator
requires Apache Hadoop of 
+Ignite distribution comes in a ZIP file that simply needs to be unzipped. The Accelerator
requires Apache Hadoop of 
 version 2.2 or above to be already installed on the system either using Apache Bigtop packages
or manually (manual installation
 just means that Apache Hadoop binary distribution must be unpacked somewhere on the system).
In case of manual 
 installation `HADOOP_HOME` environment variable must point to the installation directory
of Apache Hadoop. 
 
 > **NOTE:** You do not need any Apache Hadoop processes to be started, you only need to
deploy the Apache Hadoop 
-> distribution on your system. Nevertheless you can run Apache Hadoop jobs with GridGain's
Accelerator over HDFS,
+> distribution on your system. Nevertheless you can run Apache Hadoop jobs with Ignite
Accelerator over HDFS,
 > in this case up and running HDFS infrastructure will be needed.
 
 The Accelerator comes with command line setup tool `bin/setup-hadoop.sh` (`bin/setup-hadoop.bat`
on Windows) which 
@@ -35,14 +35,14 @@ Installation requirements:
 > **NOTE:** On Windows platform Apache Hadoop client requires `JAVA_HOME` path to not
contain space characters.
 > Java installed to `C:\\Program Files\` will not work, install JRE to correct location
and point `JAVA_HOME` there.
 
-### 2.1 Check GridGain Installation
+### 2.1 Check Apache Ignite Installation
 
-After setup script successfully completed, you can execute the GridGain startup script.
-The following command will startup GridGain node with default configuration using multicast
node discovery.
+After setup script successfully completed, you can execute the Ignite startup script.
+The following command will startup Ignite node with default configuration using multicast
node discovery.
 
     bin/ggstart.{sh|bat}
 
-If GridGain was installed successfully, the output from above commands should produce no
exceptions or errors.
+If Ignite was installed successfully, the output from above commands should produce no exceptions
or errors.
 Note that you may see some other warnings during startup, but this is OK as they are meant
to inform that certain
 functionality is turned on or off by default.
 
@@ -51,49 +51,39 @@ Here is an example of log printout when 2 nodes join topology:
 
     ... Topology snapshot [nodes=2, CPUs=8, hash=0xD551B245]
 
-You can also start GridGain Management Console, called Visor, and observe started nodes show
up on Visor Dashboard.
-To startup Visor, you should execute the following script:
+You can also start Ignite Management Console, called Visor, and observe started nodes. To
startup Visor, you should execute the following script:
 
-    bin/ggvisorcmd.{sh|bat} (Command-line, available in open source)
-    bin/ggvisorui.{sh|bat} (GUI mode, enterprise version only)
+    /bin/ggvisorcmd.{sh|bat} 
 
 ## 3. Configuration
 
-To configure GridGain nodes you can change configuration files at `config` directory of GridGain
installation. Those
-are conventional Spring files. Please refer to shipped configuration files and GridGain javadocs
for more details.
+To configure Ignite nodes you can change configuration files at `config` directory of Ignite
installation. Those are conventional Spring files. Please refer to shipped configuration files
and Ignite javadocs for more details.
 
 ### 3.1 Distributed File System Configuration
 
-GridGain has it's own distributed in-memory file system called GGFS. Hadoop jobs can use
it instead of HDFS to achieve
-maximum performance and scalability. Setting up GGFS is much simpler than HDFS, it requires
just few tweaks of 
-GridGain node configuration and does not require starting any additional processes. Default
configuration shipped 
-with the Accelerator contains one configured instance named "ggfs" which can be used as reference.
+Ignite has it's own distributed in-memory file system called IgniteFS. Hadoop jobs can use
it instead of HDFS to achieve maximum performance and scalability. Setting up GGFS is much
simpler than HDFS, it requires just few tweaks of Ignite node configuration and does not require
starting any additional processes. Default configuration shipped with the Accelerator contains
one configured instance named "ignitefs" which can be used as reference.
 
-Generally URI for GGFS which will be used by Apache Hadoop looks like:
+Generally URI for IgniteFS which will be used by Apache Hadoop looks like:
 
-    ggfs://ggfs_name@host_name
+    ignitefs://ignitefs_name@host_name
 
-Where `ggfs_name` is GGFS instance name, `host_name` is any host running GridGain node with
that GGFS instance configured. 
-For more details please refer to GGFS documentation.
+Where `ignitefs_name` is IgniteFS instance name, `host_name` is any host running Ignite node
with that IgniteFS instance configured. 
+For more details please refer to IgniteFS documentation.
 
 ### 3.2 Apache Hadoop Client Configuration
 
-To run Apache Hadoop jobs with GridGain cluster you need to configure `core-site.xml` and
`mapred-site.xml` at 
+To run Apache Hadoop jobs with Ignite cluster you need to configure `core-site.xml` and `mapred-site.xml`
at 
 `$HADOOP_HOME/etc/hadoop` directory the same way as it is done in templates shipped with
the Accelerator. 
-The setup tool `bin/setup-hadoop.{sh|bat}` will ask you to replace those files with GridGain's
templates or 
-you can find these templates at `docs/core-site.gridgain.xml` and `docs/mapred-site.gridgain.xml`
respectively
-and perform the needed configuration manually.
+The setup tool `bin/setup-hadoop.{sh|bat}` will ask you to replace those files with Ignite
templates or 
+you can find these templates at `docs/core-site.ignite.xml` and `docs/mapred-site.ignite.xml`
respectively and perform the needed configuration manually.
 
-Apache Hadoop client will need to have GridGain jar files in classpath, the setup tool will
care of that as well.
+Apache Hadoop client will need to have Ignite jar files in classpath, the setup tool will
care of that as well.
 
-## 4. Running Apache Hadoop Job With GridGain's In-Memory Accelerator
+## 4. Running Apache Hadoop Job With Ignite In-Memory Accelerator
 
-To run Apache Hadoop job with GridGain cluster you have to start one or multiple GridGain
nodes and make sure 
-they successfully discovered each other.
+To run Apache Hadoop job with Ignite cluster you have to start one or multiple Ignite nodes
and make sure they successfully discovered each other.
 
-When all the configuration is complete and GridGain nodes are started, running Apache Hadoop
job will be the same as 
-with conventional Apache Hadoop distribution except that all GridGain nodes are equal and
any of them can be treated 
-as Job Tracker and DFS Name Node.
+When all the configuration is complete and Ignite nodes are started, running Apache Hadoop
job will be the same as with conventional Apache Hadoop distribution except that all Ignite
nodes are equal and any of them can be treated as Job Tracker and DFS Name Node.
 
 To run "Word Count" example you can load some text files to GGFS using standard Apache Hadoop
tools:
  
@@ -118,28 +108,10 @@ switch Apache Hadoop client to a cluster are to fix host in default
DFS URI in `
 address in `mapred-site.xml`.
 
 ## 5. Management & Monitoring with Visor
-GridGain comes with GUI and CLI (command) based DevOps Managements Consoles delivering advance
set of management and 
-monitoring capabilities. Visor GUI is based on a standalone Java application and CLI version
is built on top of 
-Scala REPL providing fully scriptable and customizable DevOps environment.
-
-To start Visor GUI console (enterprise edition only), execute the following command:
-
-    `bin/ggvisorui.sh`
+Ignite comes with CLI (command) based DevOps Managements Console, called Visor, delivering
advance set of management and monitoring capabilities. 
 
 To start Visor in console mode you should execute the following command:
 
     `bin/ggvisorcmd.sh`
 
-On Windows, run the same commands with `.bat` extension.
-
-> **NOTE:** Visor GUI console has a much richer set of functionality over Visor command-based
console.
-> You should always prefer Visor GUI console whenever possible.
-
-Here is an example of `Visor Data Grid Tab` which provides overall view on data grid.
-
-<img width="800" src="http://www.gridgain.com/images/visor_database2.png">
-
-Here is an example of `Visor Cache Tab` which provides view on individual cache.
-
-<img width="800" src="http://www.gridgain.com/images/visor_cache.png">
-
+On Windows, run the same commands with `.bat` extension.
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/f5d64b2e/docs/hadoop_readme.pdf
----------------------------------------------------------------------
diff --git a/docs/hadoop_readme.pdf b/docs/hadoop_readme.pdf
index cb5da28..d56d950 100644
Binary files a/docs/hadoop_readme.pdf and b/docs/hadoop_readme.pdf differ

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/f5d64b2e/docs/hive-site.gridgain.xml
----------------------------------------------------------------------
diff --git a/docs/hive-site.gridgain.xml b/docs/hive-site.gridgain.xml
deleted file mode 100644
index e93be35..0000000
--- a/docs/hive-site.gridgain.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-<?xml version="1.0"?>
-<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
-<!--
-  Licensed to the Apache Software Foundation (ASF) under one or more
-  contributor license agreements.  See the NOTICE file distributed with
-  this work for additional information regarding copyright ownership.
-  The ASF licenses this file to You under the Apache License, Version 2.0
-  (the "License"); you may not use this file except in compliance with
-  the License.  You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing, software
-  distributed under the License is distributed on an "AS IS" BASIS,
-  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-  See the License for the specific language governing permissions and
-  limitations under the License.
-  -->
-
-<!--
-    This template file contains settings needed to run Apache Hive queries
-    with GridGain In-Memory Accelerator.
-
-    You can replace '$HIVE_HOME/conf/hive-site.xml' file with this one or
-    run script '$GRIDGAIN_HOME/bin/setup-hadoop.{sh|bat}' for Apache Hadoop
-    and Hive client setup.
--->
-<configuration>
-    <!--
-        GridGain requires query plan to be passed not using local resource.
-    -->
-    <property>
-        <name>hive.rpc.query.plan</name>
-        <value>true</value>
-    </property>
-</configuration>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/f5d64b2e/docs/hive-site.ignite.xml
----------------------------------------------------------------------
diff --git a/docs/hive-site.ignite.xml b/docs/hive-site.ignite.xml
new file mode 100644
index 0000000..e93be35
--- /dev/null
+++ b/docs/hive-site.ignite.xml
@@ -0,0 +1,36 @@
+<?xml version="1.0"?>
+<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+  -->
+
+<!--
+    This template file contains settings needed to run Apache Hive queries
+    with GridGain In-Memory Accelerator.
+
+    You can replace '$HIVE_HOME/conf/hive-site.xml' file with this one or
+    run script '$GRIDGAIN_HOME/bin/setup-hadoop.{sh|bat}' for Apache Hadoop
+    and Hive client setup.
+-->
+<configuration>
+    <!--
+        GridGain requires query plan to be passed not using local resource.
+    -->
+    <property>
+        <name>hive.rpc.query.plan</name>
+        <value>true</value>
+    </property>
+</configuration>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/f5d64b2e/docs/mapred-site.gridgain.xml
----------------------------------------------------------------------
diff --git a/docs/mapred-site.gridgain.xml b/docs/mapred-site.gridgain.xml
deleted file mode 100644
index c9b95c4..0000000
--- a/docs/mapred-site.gridgain.xml
+++ /dev/null
@@ -1,79 +0,0 @@
-<?xml version="1.0"?>
-<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
-<!--
-  Licensed to the Apache Software Foundation (ASF) under one or more
-  contributor license agreements.  See the NOTICE file distributed with
-  this work for additional information regarding copyright ownership.
-  The ASF licenses this file to You under the Apache License, Version 2.0
-  (the "License"); you may not use this file except in compliance with
-  the License.  You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing, software
-  distributed under the License is distributed on an "AS IS" BASIS,
-  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-  See the License for the specific language governing permissions and
-  limitations under the License.
-  -->
-
-<!--
-  Licensed under the Apache License, Version 2.0 (the "License");
-  you may not use this file except in compliance with the License.
-  You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing, software
-  distributed under the License is distributed on an "AS IS" BASIS,
-  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-  See the License for the specific language governing permissions and
-  limitations under the License. See accompanying LICENSE file.
--->
-
-<!--
-    This template file contains settings needed to run Apache Hadoop jobs
-    with GridGain In-Memory Accelerator.
-
-    You can replace '$HADOOP_HOME/etc/hadoop/mapred-site.xml' file with this one
-    to run jobs on localhost (local node can be a part of distributed cluster though).
-    To run jobs on remote host you have to change jobtracker address to the REST address
-    of any running GridGain node.
-
-    Note that GridGain jars must be in Apache Hadoop client classpath to work
-    with this configuration.
-
-    Run script '$GRIDGAIN_HOME/bin/setup-hadoop.{sh|bat}' for Apache Hadoop client setup.
--->
-
-<configuration>
-    <!-- 
-        Framework name must be set to 'gridgain'.
-    -->
-    <property>
-        <name>mapreduce.framework.name</name>
-        <value>gridgain</value>
-    </property>
-
-    <!--
-        Job tracker address must be set to the REST address of any running GridGain node.
-    -->
-    <property>
-        <name>mapreduce.jobtracker.address</name>
-        <value>localhost:11211</value>
-    </property>
-
-    <!-- Parameters for job tuning. -->
-    <!--
-    <property>
-        <name>mapreduce.job.reduces</name>
-        <value>1</value>
-    </property>
-
-    <property>
-        <name>mapreduce.job.maps</name>
-        <value>4</value>
-    </property>
-    -->
-
-</configuration>

http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/f5d64b2e/docs/mapred-site.ignite.xml
----------------------------------------------------------------------
diff --git a/docs/mapred-site.ignite.xml b/docs/mapred-site.ignite.xml
new file mode 100644
index 0000000..c9b95c4
--- /dev/null
+++ b/docs/mapred-site.ignite.xml
@@ -0,0 +1,79 @@
+<?xml version="1.0"?>
+<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+  -->
+
+<!--
+  Licensed under the Apache License, Version 2.0 (the "License");
+  you may not use this file except in compliance with the License.
+  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License. See accompanying LICENSE file.
+-->
+
+<!--
+    This template file contains settings needed to run Apache Hadoop jobs
+    with GridGain In-Memory Accelerator.
+
+    You can replace '$HADOOP_HOME/etc/hadoop/mapred-site.xml' file with this one
+    to run jobs on localhost (local node can be a part of distributed cluster though).
+    To run jobs on remote host you have to change jobtracker address to the REST address
+    of any running GridGain node.
+
+    Note that GridGain jars must be in Apache Hadoop client classpath to work
+    with this configuration.
+
+    Run script '$GRIDGAIN_HOME/bin/setup-hadoop.{sh|bat}' for Apache Hadoop client setup.
+-->
+
+<configuration>
+    <!-- 
+        Framework name must be set to 'gridgain'.
+    -->
+    <property>
+        <name>mapreduce.framework.name</name>
+        <value>gridgain</value>
+    </property>
+
+    <!--
+        Job tracker address must be set to the REST address of any running GridGain node.
+    -->
+    <property>
+        <name>mapreduce.jobtracker.address</name>
+        <value>localhost:11211</value>
+    </property>
+
+    <!-- Parameters for job tuning. -->
+    <!--
+    <property>
+        <name>mapreduce.job.reduces</name>
+        <value>1</value>
+    </property>
+
+    <property>
+        <name>mapreduce.job.maps</name>
+        <value>4</value>
+    </property>
+    -->
+
+</configuration>


Mime
View raw message