Skip to main content

Calling elasticsearch in Play! java stack.

Calling elasticsearch in Play! java stack.

ㅇ index
0. play! installation
http://www.playframework.com/documentation/2.2.x/Installing
just download and make PATH
1. making play! app (esproject)
2. changing the app for eclipse
3. add elasticsearch libraries to play!
4. making the route for test (put elasticsearch index)
5. coding with sample util class
6. debugging the play!
7. run elasticsearch servers
8. monitoring elasticsearch
9. check out query result with java API


1. making play! app (esproject)
$> play new esproject
What is the application name? [esproject]
>(enter)
Which template do you want to use for this new application?
 1             - Create a simple Scala application
 2             - Create a simple Java application
> 2
OK, application esproject is created.
Have fun!

2. changing the app for eclipse

$> cd esproject/
$> play eclipse
~~~
[info] Successfully created Eclipse project files for project(s):
[info] esproject

3. add elasticsearch libraries to play!

3.1 mkdir /esproject/lib

3.2 copy jars to lib path
/esproject/lib/elasticsearch-1.0.0.jar
/esproject/lib/lucene-analyzers-common-4.6.1.jar
/esproject/lib/lucene-codecs-4.6.1.jar
/esproject/lib/lucene-core-4.6.1.jar
/esproject/lib/lucene-grouping-4.6.1.jar
/esproject/lib/lucene-highlighter-4.6.1.jar
/esproject/lib/lucene-join-4.6.1.jar
/esproject/lib/lucene-memory-4.6.1.jar
/esproject/lib/lucene-misc-4.6.1.jar
/esproject/lib/lucene-queries-4.6.1.jar
/esproject/lib/lucene-queryparser-4.6.1.jar
/esproject/lib/lucene-sandbox-4.6.1.jar
/esproject/lib/lucene-spatial-4.6.1.jar
/esproject/lib/lucene-suggest-4.6.1.jar

3.3 modify classpath
/esproject/.classpath

<classpathentry kind="lib" path="lib/elasticsearch-1.0.0.jar"/>
<classpathentry kind="lib" path="lib/lucene-core-4.6.1.jar"/>
<classpathentry kind="lib" path="lib/lucene-analyzers-common-4.6.1.jar"/>
<classpathentry kind="lib" path="lib/lucene-codecs-4.6.1.jar"/>
<classpathentry kind="lib" path="lib/lucene-queries-4.6.1.jar"/>
<classpathentry kind="lib" path="lib/lucene-memory-4.6.1.jar"/>
<classpathentry kind="lib" path="lib/lucene-highlighter-4.6.1.jar"/>
<classpathentry kind="lib" path="lib/lucene-queryparser-4.6.1.jar"/>
<classpathentry kind="lib" path="lib/lucene-sandbox-4.6.1.jar"/>
<classpathentry kind="lib" path="lib/lucene-suggest-4.6.1.jar"/>
<classpathentry kind="lib" path="lib/lucene-misc-4.6.1.jar"/>
<classpathentry kind="lib" path="lib/lucene-join-4.6.1.jar"/>
<classpathentry kind="lib" path="lib/lucene-grouping-4.6.1.jar"/>
<classpathentry kind="lib" path="lib/lucene-spatial-4.6.1.jar"/>

3.4 modify configuration file
/esproject/conf/application.conf

# elasticsearch
elasticsearch.clusterName = locketCast
elasticsearch.nodes = "localhost:9300,localhost:9301,localhost:9302"

4. making the route for test (put elasticsearch index)
/esproject/conf/routes

# http://localhost:9000/test/putIndex?id=1&indexString={"user_id":"doohee323", "action":"search", "data":"facebook Feed"}
GET     /test/putIndex        controllers.Esearch.putIndex(id:Long, indexString:String)

5. coding with sample util class
/esproject/app/controllers/Esearch.java
/esproject/app/services/ElasticsearchService.java

6. debugging the play!
6.1 run play! in debug mode
$> play debug
[esproject] $ Listening for transport dt_socket at address: 9999
[esproject] $ run

6.2 run eclipse debugger
eclipse Debug Configurations
Remote Java Application > new >
- Project : esproject
- Host : localhost
- Port : 9999

7. run elasticsearch servers
/data1/elasticsearch/node1> ./start.sh
/data1/elasticsearch/node2> ./start.sh
/data1/elasticsearch/node3> ./start.sh

browser call with 'http://localhost:9000/test/putIndex?id=1&indexString={"user_id":"doohee323", "action":"search", "data":"facebook Feed"}'

8. monitoring elasticsearch
8.1 check out the indexes
http://localhost:9200/_plugin/kopf

8.2 check out query result with rest API
http://localhost:9200/_search?q=user_id:doohee323
-> http://localhost:9200/updatelogs/20140428/_search
-> http://localhost:9200/updatelogs/20140428/_count?q=user_id:doohee323

9. check out query result with java API
/esproject/conf/routes
# http://localhost:9000/test/getIndex?queryString={"user_id":"doohee323"}
GET     /test/getIndex        controllers.Esearch.getIndex(queryString:String)

or execute /esproject/test/ElasticTest.java

cf.
- source: https://github.com/doohee323/esproject
- elasticsearch: https://github.com/doohee323/hanb-elasticsearch-beginner




Comments

Post a Comment

Popular posts from this blog

Install CoreOs on linode without VM

Install CoreOs on linode without VM 1. Add a Linode 2. Create a new Disk   CoreOS 3. Rescue > Reboot into Rescue Mode 4. Remote Access   Launch Lish Console 5. make an install script cat <<'EOF1' > install.sh # add needed package sudo apt-get update sudo apt-get install -y curl wget whois sudo apt-get install -y ca-certificates #sudo apt-get install gawk -y # get discovery url discoveryUrl=`curl https://discovery.etcd.io/new` # write cloud-config.yml cat <<EOF2 > cloud-config.yml #cloud-config users:   - name: core     groups:       - sudo       - docker coreos:   etcd:     name: node01     discovery: $discoveryUrl hostname: node01 EOF2 # get the coreos installation script #wget https://raw.github.com/coreos/init/master/bin/coreos-install wget https://raw.githubusercontent.com/coreos/init/master/bin/coreos-install # run installation chmod 75...
31 comments
Read more

Amazon RDS Blue/Green Deployments

In order to avoid some errors I experienced when proceeding as described in the official documentation, I describe what I did in order. 1) Modify parameters of source_database * error: Blue Green Deployments requires cluster parameter group has binlog enabled. RDS Parameter groups: source-params-group binlog_format => MIXED mysql> show global variables like 'binlog_format'; 2) Insert a row after rebooting the source database, to avoid this error. * error: Correct the replication errors and then switch over. Read Replica Replication Error - IOError: 1236, reason: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file' => To Fix: You need to change the data in the source database. INSERT INTO dummy_table ( `favorite_id` , `favorite_order` , `user_id` , `board_id` ) VALUES ('100001', '1', '11111', '11111'); 3) Modify the param...
Post a Comment
Read more

실리콘밸리 구직 체험기2_201505 - 3. 새로운 위기

실리콘밸리 구직 체험기2_201505 - 3. 새로운 위기 우리는 지난 1년간 lockscreen app과 messenger app을 만들었습니다. 나는 backend restful API를 만들고 cms를 node.js, angular.js로 만들었다. 또한 AWS 인스턴스를 관리했습니다. 마지막 몇달 동안 기존 lockscreen 앱과 CMS 관리 대신에 메신저 앱에 집중했습니다. 한국에서는 매출과 이익을 내지 않으면 투자를 받을 수 없는 환경이지만 매출 없이 유저수 증가에만 집중하는 모습이 참 생소했습니다. 우리는 사용자의 행태를 확인하기 위해서 BI툴을 이용해서 사용자 수와 retention rate 등을 추적하고 새로운 기능에 대해 사용자의 반응을 점검하면서 기획을 수시로 바꿨습니다. 많은 기능을 새로 만들고 ab test를 통해서 또 많이 폐기 했다. 실제 만든 기능 중에 절반 이상은 버려 졌습니다. locket앱은 2014년 google store의 베스트 앱으로 선정되기도 했다. 그러나 사실 이 시점에 이미 우리는 메신저 앱에 올인 하고 있었습니다. https://www.facebook.com/photo.php?fbid=10204452594066393&set=a.2225490048257.118046.1577949323&type=1 우리가 만든 메신저 앱은 초반의 반응이 워낙 좋아서 정체되었던 lockscreen 유저수를 단번에 따라 잡았습니다. 특히 Retention Rate 이 좋아서 사용자들의 제대로 사용하고 있다고 생각했습니다. 잠깐이지만 google play 에 featured 되고, 인도에 가입 지원을 했을 때 사용자 수가 급증하기도 했습니다. https://www.facebook.com/photo.php?fbid=10204901853057587&set=a.2225490048257.118046.1577949323&type=1 그 시...
Post a Comment
Read more