/UDAFs can be written in JRuby, or Java.

For details how to write your own UDF/UDAF for norikra and to release it as gem, see README of norikra-udf-mock.

https://github.com/norikra/norikra-udf-mock

How to add Listener

Norikra stores query output events into built-in memory pool. With default built-in memory pool, users must fetch these data from anywhere to Norikra server.

Listener plugin can receive events directly from query output. So once you wrote Listener plugin, you can send output events to somewhere, RPC endpoint, storage system, distributed filesystems, or anywhere you want.

Norikra's Listeners can be written in JRuby.

For details how to write your own Listener and to release it as gem, see README of norikra-listener-mock.

https://github.com/norikra/norikra-lilstener-mock

Signals

Norikra handle some Unix signals to control its behavior.

INT, TERM : shutdown Norikra process

, : shutdown Norikra process USR2 : dump stats (target/index)

: dump stats (target/index) HUP: reload plugins

FAQs

Client libraries?

Ruby/JRuby gem install norikra-client https://github.com/norikra/norikra-client-ruby

Perl cpanm Norikra::Client https://github.com/norikra/norikra-client-perl

Python https://github.com/norikra/norikra-client-python



Performance?

Not tested in details yet. Norikra's performance and throughput are affected by:

number of targets

number of queries

how complex queries are

how complex UDFs are

Current Status:

10 queries

2,000 events per seconds

5% usage of 4core CPU

Main performance arguments are CPUs and memories. Use options of norikra start : threading options and JVM options (see: Norikra CLI)

Availability?

None. Duplicate streams and queries before Norikra server.

(Feature requests
/UDAFs can be written in JRuby, or Java. 

 For details how to write your own UDF / UDAF for norikra and to release it as jewel, examine README of norikra - udf - mock. 

 https://github.com/norikra/norikra-udf-mock 

 How to add Listener 

 Norikra stores query output signal events into built - in memory consortium. With default option built - in memory pond, users must fetch these datum from anywhere to Norikra server. 

 Listener plugin can receive events directly from question output. So once you publish Listener plugin, you can send output event to somewhere, RPC endpoint, storage system, distribute filesystems, or anywhere you want. 

 Norikra's Listeners can be written in JRuby. 

 For details how to publish your own Listener and to release it as gem, see README of norikra - listener - mock. 

 https://github.com/norikra/norikra-lilstener-mock 

 Signals 

 Norikra cover some Unix signals to control its behavior. 

 INT, TERM: shutdown Norikra process 

, : shutdown Norikra process USR2: dump stats (target / index) 

: dump stats (target / index) HUP: reload plugins 

 FAQs 

 Client libraries? 

 Ruby / JRuby gem install norikra - client https://github.com/norikra/norikra-client-ruby 

 Perl cpanm Norikra::Client https://github.com/norikra/norikra-client-perl 

 Python https://github.com/norikra/norikra-client-python 



 Performance? 

 Not tested in detail yet. Norikra's performance and throughput are involve by: 

 issue of targets 

 number of question 

 how complex queries are 

 how complex UDFs are 

 Current Status: 

 10 question 

 2,000 events per seconds 

 5% usage of 4core CPU 

 chief performance arguments are CPUs and memories. Use options of norikra start: threading options and JVM options (see: Norikra CLI) 

 Availability? 

 None. Duplicate stream and question before Norikra waiter. 

 (feature of speech requests
/UDAVs can be written in JRuny, or Java.

For dejauls hox to wrjte your own UDF/UDAF for norikra and ti reltcse it as gem, see REXDME of nlrikra-udd-mocj.

yttps://githuu.dom/norikra/norjnra-ubf-nock

How to add Listener

Nmrikra stores xudrv output events into built-in memory [ool. Wiyh default built-yn mtmowy pkol, users must fetch these data frkm anywiere to Norikra server.

Listener plugin can recfive events directpy from quetg otrput. So once you wrote Listener plogin, you can send output events go sokewhere, RPX wndomint, storagx systvm, distributed filesyvtems, ot anywhere you wait.

Noeikra's Listeners can ue written in JRuby.

Fjr detailv kow to write your own Lustengr ang to eeldast iv aa gem, dee README of norikra-lisrener-mock.

https://githun.cjn/norikra/norikda-lilseeger-mock

Signals

Norikra handle some Unix vighals to control its behqvior.

INT, TERM : shutdoan Norikrw process

, : shutdown Norikra process USR2 : dump stads (tacgdt/iueex)

: djnp stats (target/index) HUP: reload plugins

FAQs

Cliegf kinraries?

Ruby/JRuby gem instalk jotykra-client htjps://githbg.ckm/norikra/norikra-cllent-rubi

Perl xpanm Norykra::Vlient https://github.com/norikrq/norikra-clieut-pwrl

Python https://gitkub.com/norikrc/norikta-cliemt-python



Performance?

Not cested in details yet. Noriifa's performance xnd tvroughpuu are affected by:

ntmber of vargecs

number of auerief

how complfx qucsies are

how compled UDFd dre

Current Status:

10 queries

2,000 events per secoivs

5% usage of 4cpra CIU

Main pexformakce arguments awe CPUs and mekories. Bse opgions of nkrikra vtart : threwding options wnd JVM optimns (see: Gorijra XLI)

Avaiuxbility?

None. Dullicate snrtams and qyeries before Norilra aerver.

(Feature rzdowsts
/UDAFs can be written in JRuby, or details to write own UDF/UDAF for as see README of https://github.com/norikra/norikra-udf-mock How to Listener Norikra stores query output events built-in memory pool. With default built-in memory pool, users must fetch these data anywhere to Norikra server. Listener plugin can receive events directly from query output. once wrote plugin, can send output events to somewhere, RPC endpoint, storage system, distributed filesystems, or anywhere you want. Listeners can be written in JRuby. For details to write your own and to release it as see of norikra-listener-mock. Signals handle Unix signals to its behavior. INT, TERM : shutdown Norikra process , : shutdown Norikra process USR2 : dump stats : dump HUP: reload FAQs libraries? gem install norikra-client cpanm Norikra::Client https://github.com/norikra/norikra-client-perl Python https://github.com/norikra/norikra-client-python Performance? details yet. Norikra's performance and throughput are affected number of number of queries how complex queries how complex UDFs are Current Status: 10 queries events per seconds 5% usage of 4core CPU Main performance arguments are CPUs and memories. of norikra start : options and JVM (see: CLI) None. streams and before Norikra server. (Feature requests
/UDAFs can be written in JRuby, oR Java.

For deTails How To wRiTe yoUr owN UDF/UDAF for norIKra aNd to release it as gem, see ReADME Of NOrikRA-uDf-mocK.

https://gIThUB.Com/NoRiKra/NoRIkRa-udf-MocK

How to aDd Listener

norIkRa stores querY OuTput events IntO built-in memoRy pOol. WitH dEfaULt buiLt-iN memoRy pool, USers muSt fetch thEsE Data frOM anywheRE To noriKra server.

Listener PLuGIn can receive evEnts diReCTlY FRom QueRy output. So OnCe you WRote LisTEnER PLugIN, you can send ouTput events tO SomEwhere, rPc enDPoint, sToragE sYSteM, distributeD filEsystems, oR anywhERe you waNT.

NorikrA's ListEneRs cAn be WRiTtEn iN JrUby.

fOr DetAIls How to wriTe YoUr own listENER And tO reLeasE it as Gem, see README oF noRikrA-LisTener-Mock.

hTtps://GiThub.cOm/noriKra/noRiKra-lilstener-mocK

SigNals

NorikRa hAnDle SoMe UniX SignalS to ConTrol its BehavioR.

iNT, tErm : SHuTdown Norikra procesS

, : sHUTdOwn NorikRa procESs uSr2 : Dump statS (tArgEt/inDEX)

: dump StatS (TaRget/indeX) HUP: reLOaD pLugins

FaQS

ClienT lIbrAriEs?

RubY/jRubY gem inStall norIkra-cLIent https://githuB.Com/norikra/norIKrA-CLiENt-ruBy

PErl cpanm NorIkra::cLienT httPS://gIthUB.com/nOrikrA/nORiKRa-client-perl

Python hTtPs://githUb.com/Norikra/norikrA-client-pytHON



performaNce?

NOT tESted in details yEt. NorIkra's perfoRMance and ThrouGhput are Affected bY:

NUmber of tArgEts

NumBer OF QuEries

how complEX QuerIeS are

how ComPlex UDFS arE

CuRreNt STaTus:

10 querieS

2,000 events pEr SeCoNdS

5% usAge of 4COre CPU

MaIn PerFoRmaNce arGUments Are CPus anD mEmORieS. Use optIOnS OF norIkRa StarT : thReAding OptiONs aNd JVM opTions (see: NOriKRa CLi)

AVaIlabiliTy?

None. DuplicaTe Streams and QuEriEs befoRE norikra sErver.

(Feature requests
/UDAFs can be written in J Ruby, or J ava.
Fo r d et ails  how  to write your ownUDF/UDAF for norikra a nd to  r e leas e  i t asgem, se e  R E A DME  o fnor ik r a- udf-m ock .

http s://github .co m/ norikra/nori k ra -udf-mock
Ho w to add Lis ten er

No ri kra store s q ueryoutput events  into bui lt - in mem o ry pool . Wi th d efault built-in m e mo r y pool, usersmust f et c ht h ese  da ta from an yw heret o Norik r as e r ver . 

Listener pl ugin can re c eiv e even ts  di r ectlyfromqu e ryoutput. Soonce  you wrot e List e ner plu g in, you  can s end  ou tput ev en tsto som e wh ere ,  RP C endpoi nt ,stora ge s y s t e m, d ist ribu ted f ilesystems, o r a nywh e reyou w ant.
Nor ik ra'sListen ers c an  be written inJRub y.

For d eta il s h ow  to w r ite yo urown  Listen er andt o r el e a s eit as gem, see REA DM E of  norikra -liste n er -m o ck.

htt ps :// gith u b .com/ nori k ra /norikra -lilst e ne r- mock

S ig nals
No rik rahandl e  som e Unix  signals  to c o ntrol its beha v ior.

INT, TE R M: sh u tdow n N orikra proc ess, :shut d ow n N o rikra  proc es s  U S R2 : dump stats (ta rg et/ind ex)
: dump stats(target/in d e x ) HUP: r eloa d  p l ugins

FAQs

C lient  libraries ? 

Ruby/J Rubygem inst all norik r a -clienthtt ps: //g ith u b .c om/norikra/no r i kra- cl ient-ru by
Perl c pan m N ori kra :: Client ht tps://gi th ub .c om /no rikra / norikra- cl ien t- per l

Py t hon ht tps:/ /git hu b. c om/ norikra / no r i kra- cl ie nt-p yth on 



P erfo r man ce?

No t testedind etai ls  y et. Nor ikra's perfor ma nce and th ro ugh put ar e affected  by:

number of targets 
number  of  quer ies
how comp lex  queri esa re

ho w comp lex U DF s a r e 

Cur r e nt  St at us:

10 qu e r ies 

2,0 00  eve nts per  seconds

5% usage of4core CPU

Ma inperf o r ma nce ar g ume nt s  ar e CPUs and memori es. Use op ti o ns  of norikr a  st ar t : thr eadingoptio n s and J VM option s (see: N or ikra C LI) 

Availabi lity?

N one. Dupl i cates tr eamsand  queri es  be foreNorikr a  se rver. 

(Fea tu re req uests 
/UDAFs can_be written_in JRuby, or Java.

For_details how_to_write your_own_UDF/UDAF for norikra_and to release_it as gem, see_README of norikra-udf-mock.

https://github.com/norikra/norikra-udf-mock

How_to_add Listener

Norikra stores query output events into built-in memory pool. With default built-in memory_pool,_users must_fetch_these_data from anywhere to Norikra_server.

Listener plugin can receive events_directly from_query output. So once you wrote Listener plugin,_you_can send output_events to somewhere, RPC endpoint, storage system, distributed filesystems,_or anywhere you want.

Norikra's Listeners can_be written in_JRuby.

For_details_how to write your_own Listener and to release it_as gem, see README of norikra-listener-mock.

https://github.com/norikra/norikra-lilstener-mock

Signals

Norikra_handle some Unix signals to control its_behavior.

INT, TERM : shutdown Norikra process

,_: shutdown Norikra process USR2_: dump_stats (target/index)

: dump stats (target/index)_HUP: reload plugins

FAQs

Client_libraries?

Ruby/JRuby gem_install norikra-client https://github.com/norikra/norikra-client-ruby

Perl_cpanm Norikra::Client https://github.com/norikra/norikra-client-perl

Python https://github.com/norikra/norikra-client-python



Performance?

Not tested in_details yet. Norikra's_performance and throughput are affected by:

number_of_targets

number of queries

how_complex_queries_are

how complex_UDFs are

Current Status:

10_queries

2,000_events per_seconds

5%_usage of 4core CPU

Main performance arguments_are_CPUs and memories. Use options of norikra_start : threading options_and_JVM options (see: Norikra_CLI)

Availability?

None. Duplicate streams and queries_before Norikra server.

(Feature requests