{"id":37567,"date":"2019-10-31T22:18:22","date_gmt":"2019-10-31T19:18:22","guid":{"rendered":"https:\/\/prohoster.info\/blog\/apache-nifi-kratkij-obzor-vozmozhnostej-na-praktike\/"},"modified":"2019-10-31T22:18:22","modified_gmt":"2019-10-31T19:18:22","slug":"apache-nifi-kratkij-obzor-vozmozhnostej-na-praktike","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/apache-nifi-kratkij-obzor-vozmozhnostej-na-praktike","title":{"rendered":"Apache NIFI \u2014 Nj\u00eb p\u00ebrmbledhje e shkurt\u00ebr e mund\u00ebsive n\u00eb praktik\u00eb","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Hyrje<\/h3>\n

<\/p>\n

N\u00eb vendin tim aktual t\u00eb pun\u00ebs, pata rastin t\u00eb njoh k\u00ebt\u00eb teknologji. T\u00eb filloj me nj\u00eb histori t\u00eb shkurt\u00ebr. gjat\u00eb nj\u00eb mbledhjeje, ekipit ton\u00eb iu tha se duhej t\u00eb krijonim nj\u00eb integrim me nj\u00eb sistem t\u00eb njohur<\/em>. Integrimi n\u00ebnkuptonte se ky sistem i njohur do t\u00eb na d\u00ebrgonte k\u00ebrkesa p\u00ebrmes HTTP n\u00eb nj\u00eb endpoint t\u00eb caktuar, dhe ne, \u00e7udit\u00ebrisht, do t\u00eb d\u00ebrgonim p\u00ebrgjigje n\u00eb form\u00ebn e nj\u00eb mesazhi SOAP. Duket e thjesht\u00eb dhe triviale. Nga kjo del se duhet...<\/a><\/noindex><\/p>\n

<\/p>\n

Detyra<\/h3>\n

<\/p>\n

Krijoni 3 sh\u00ebrbime. Sh\u00ebrbimi i par\u00eb \u00ebsht\u00eb Sh\u00ebrbimi i p\u00ebrdit\u00ebsimit t\u00eb DB. Ky sh\u00ebrbim, kur merr t\u00eb dh\u00ebna t\u00eb reja nga nj\u00eb sistem tjet\u00ebr, p\u00ebrdit\u00ebson t\u00eb dh\u00ebnat n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave dhe gjeneron nj\u00eb skedar n\u00eb formatin CSV, p\u00ebr ta transferuar n\u00eb sistemin n\u00eb vijim. Aktivizohet n\u00ebnpik\u00eb t\u00eb dyt\u00eb t\u00eb sh\u00ebrbimit \u2014 Sh\u00ebrbimi i transportit p\u00ebrmes FTP, i cili merr skedarin e d\u00ebrguar, e validon at\u00eb dhe e ruan n\u00eb nj\u00eb ruajt\u00ebs skedar\u00ebsh p\u00ebrmes FTP. Sh\u00ebrbimi i tret\u00eb \u2014 Sh\u00ebrbimi i d\u00ebrgimit t\u00eb t\u00eb dh\u00ebnave tek konsumatori, punon asinkronisht me dy t\u00eb par\u00ebt. Ai merr nj\u00eb k\u00ebrkes\u00eb nga nj\u00eb sistem t\u00eb jasht\u00ebm, p\u00ebr t\u00eb marr\u00eb skedarin p\u00ebr t\u00eb cilin u p\u00ebrmend m\u00eb sip\u00ebr, merr skedarin e gatsh\u00ebm t\u00eb p\u00ebrgjigjes, e modifikon at\u00eb (p\u00ebrdit\u00ebson fushat id, description, linkToFile) dhe d\u00ebrgon p\u00ebrgjigjen n\u00eb form\u00ebn e nj\u00eb mesazhi SOAP. Pra, n\u00eb p\u00ebrgjith\u00ebsi, pamja \u00ebsht\u00eb k\u00ebshtu: dy sh\u00ebrbimet e para fillojn\u00eb pun\u00ebn e tyre vet\u00ebm kur vijn\u00eb t\u00eb dh\u00ebna p\u00ebr p\u00ebrdit\u00ebsim. Sh\u00ebrbimi i tret\u00eb punon vazhdimisht pasi ka shum\u00eb konsumator\u00eb t\u00eb informacionit, rreth 1000 k\u00ebrkesa p\u00ebr t\u00eb marr\u00eb t\u00eb dh\u00ebna n\u00eb minut\u00eb. Sh\u00ebrbimet jan\u00eb t\u00eb aksesueshme vazhdimisht dhe instancat e tyre jan\u00eb t\u00eb vendosura n\u00eb mjedise t\u00eb ndryshme, si test, demo, para-l\u00ebshim dhe prodhim. M\u00eb posht\u00eb \u00ebsht\u00eb paraqitur skema e funksionimit t\u00eb k\u00ebtyre sh\u00ebrbimeve. Menj\u00ebher\u00eb po shpjegoj se disa detaje jan\u00eb thjeshtuar p\u00ebr t\u00eb shmangur kompleksitetin e tepruar.<\/p>\n

<\/p>\n

\"Apache<\/p>\n

<\/p>\n

Thellimi teknik<\/h3>\n

<\/p>\n

Gjat\u00eb planifikimit t\u00eb zgjidhjes s\u00eb problemit, s\u00eb pari vendos\u00ebm t\u00eb zhvillojm\u00eb aplikacione n\u00eb java duke p\u00ebrdorur Spring framework, me balancuesin Nginx, baz\u00ebn e t\u00eb dh\u00ebnave Postgres dhe gj\u00ebra t\u00eb tjera teknike e jo shum\u00eb. Duke qen\u00eb se koha p\u00ebr t\u00eb punuar n\u00eb zgjidhjen teknike lejonte shqyrtimin e qasjeve t\u00eb tjera p\u00ebr k\u00ebt\u00eb problem, v\u00ebmendja u p\u00ebrqendrua n\u00eb teknologjin\u00eb Apache NIFI, e cila \u00ebsht\u00eb b\u00ebr\u00eb e njohur n\u00eb disa qarqe. T\u00eb them t\u00eb drejt\u00ebn, kjo teknologji na lejoi t\u00eb v\u00ebm\u00eb re k\u00ebto 3 sh\u00ebrbime. N\u00eb k\u00ebt\u00eb artikull do t\u00eb p\u00ebrshkruhet zhvillimi i sh\u00ebrbimit t\u00eb transportit t\u00eb skedareve dhe sh\u00ebrbimit t\u00eb transferimit t\u00eb t\u00eb dh\u00ebnave te konsumatori; megjithat\u00eb, n\u00ebse artikulli do t\u00eb pranohet mir\u00eb, do t\u00eb shkruaj p\u00ebr sh\u00ebrbimin e p\u00ebrdit\u00ebsimit t\u00eb t\u00eb dh\u00ebnave n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave.<\/p>\n

<\/p>\n

\u00c7far\u00eb \u00ebsht\u00eb kjo?<\/h3>\n

<\/p>\n

NIFI paraqet nj\u00eb arkitektur\u00eb t\u00eb shp\u00ebrndar\u00eb p\u00ebr ngarkimin dhe p\u00ebrpunimin e t\u00eb dh\u00ebnave n\u00eb m\u00ebnyr\u00eb t\u00eb shpejt\u00eb dhe paralele, nj\u00eb num\u00ebr t\u00eb madh pluginsh p\u00ebr burimet dhe transformimet, versionimin e konfigurimeve dhe shum\u00eb m\u00eb tep\u00ebr. Nj\u00eb bonus i k\u00ebndsh\u00ebm \u00ebsht\u00eb se \u00ebsht\u00eb shum\u00eb e leht\u00eb p\u00ebr t'u p\u00ebrdorur. Proceset triviale, si getFile, sendHttpRequest dhe t\u00eb tjera \u2014 mund t\u00eb paraqiten si katror\u00eb. \u00c7do katror p\u00ebrfaq\u00ebson nj\u00eb proces, nd\u00ebrveprimi i t\u00eb cilit mund t\u00eb shihet n\u00eb figur\u00ebn m\u00eb posht\u00eb. Dokumentacioni m\u00eb i detajuar mbi nd\u00ebrveprimin e konfigurimit t\u00eb proceseve \u00ebsht\u00eb shkruar k\u00ebtu<\/a><\/noindex> , p\u00ebr ata q\u00eb flasin rusisht \u2014 k\u00ebtu<\/a><\/noindex>. N\u00eb dokumentacion, \u00ebsht\u00eb shkruar shum\u00eb mir\u00eb se si t\u00eb shkarkoni dhe t\u00eb lan\u00e7oni NIFI, si dhe si t\u00eb krijoni procese, ato jan\u00eb katror\u00ebt
\nIdeja p\u00ebr t\u00eb shkruar nj\u00eb artikull lindi pas k\u00ebrkimeve t\u00eb zgjatura dhe strukturuar t\u00eb informacionit t\u00eb marr\u00eb n\u00eb di\u00e7ka t\u00eb kuptueshme, si dhe d\u00ebshira p\u00ebr t\u00eb leht\u00ebsuar pak jet\u00ebn e zhvilluesve t\u00eb ardhsh\u00ebm.<\/p>\n

<\/p>\n

Shembuj<\/h3>\n

<\/p>\n

K\u00ebtu \u00ebsht\u00eb nj\u00eb shembull i m\u00ebnyr\u00ebs si nd\u00ebrveprojn\u00eb katrat me nj\u00ebri-tjetrin. Skema e p\u00ebrgjithshme \u00ebsht\u00eb mjaft e thjesht\u00eb: Marrim nj\u00eb k\u00ebrkes\u00eb HTTP (n\u00eb teorin\u00eb me nj\u00eb skedar n\u00eb trupin e k\u00ebrkes\u00ebs. P\u00ebr t\u00eb demonstruar mund\u00ebsit\u00eb e NIFI, n\u00eb k\u00ebt\u00eb shembull k\u00ebrkesa fillon procesin e marrjes s\u00eb skedarit nga depoja lokale), pastaj d\u00ebrgojm\u00eb nj\u00eb p\u00ebrgjigje prapa q\u00eb k\u00ebrkesa \u00ebsht\u00eb pranuar, n\u00eb m\u00ebnyr\u00eb paralele fillon procesi i marrjes s\u00eb skedarit nga depoja dhe m\u00eb pas procesi i transferimit t\u00eb tij p\u00ebrmes FTP n\u00eb depo. Duhet t\u00eb theksohet se proceset nd\u00ebrveprojn\u00eb me nj\u00ebri-tjetrin p\u00ebrmes asaj q\u00eb quhet flowFile. Kjo \u00ebsht\u00eb nj\u00eb entitet bazik n\u00eb NIFI, i cili ruan ATTRIBUTET dhe p\u00ebrmbajtjen. P\u00ebrmbajtja \u2014 t\u00eb dh\u00ebnat q\u00eb p\u00ebrfaq\u00ebsohen nga skedari i rrjedh\u00ebs. Pra, n\u00eb m\u00ebnyr\u00eb t\u00eb thjesht\u00eb, n\u00ebse keni marr\u00eb nj\u00eb skedar nga nj\u00eb katror dhe e d\u00ebrgoni n\u00eb nj\u00eb tjet\u00ebr, p\u00ebrmbajtja do t\u00eb jet\u00eb skedari juaj.<\/p>\n

<\/p>\n

\"Apache<\/p>\n

<\/p>\n

Si\u00e7 mund ta vini re \u2014 n\u00eb k\u00ebt\u00eb skic\u00eb \u00ebsht\u00eb ilustruar procesi i p\u00ebrgjithsh\u00ebm. HandleHttpRequest \u2014 pranon k\u00ebrkesat, ReplaceText \u2014 gjeneron trupin e p\u00ebrgjigjes, HandleHttpResponse \u2014 jep p\u00ebrgjigjen. FetchFile \u2014 merr skedarin nga depoja dhe e d\u00ebrgon tek katrori PutSftp \u2014 e vendos k\u00ebt\u00eb skedar n\u00eb FTP, n\u00eb adres\u00ebn e sh\u00ebnuar. Tani le t\u00eb flasim m\u00eb shum\u00eb mbi k\u00ebt\u00eb proces. <\/p>\n

<\/p>\n

N\u00eb k\u00ebt\u00eb rast \u2014 k\u00ebrkesa \u00ebsht\u00eb gjith\u00e7ka fillim. Le t\u00eb shikojm\u00eb parametrat e saj t\u00eb konfigurimit. <\/p>\n

<\/p>\n

\"Apache<\/p>\n

\nK\u00ebtu gjith\u00e7ka \u00ebsht\u00eb mjaft triviale p\u00ebrve\u00e7 StandartHttpContextMap \u2014 kjo \u00ebsht\u00eb nj\u00eb sh\u00ebrbim q\u00eb lejon d\u00ebrgimin dhe pranimin e k\u00ebrkesave. M\u00eb shum\u00eb detaje dhe madje me shembuj mund t\u00eb shikoni \u2014 k\u00ebtu<\/a><\/noindex><\/p>\n

M\u00eb pas do t\u00eb shohim parametrat e konfigurimit t\u00eb ReplaceText katrorit. Duhet t\u00eb kushtohet v\u00ebmendje ReplacementValue \u2014 ky \u00ebsht\u00eb elementi q\u00eb do t\u2019i kthehet p\u00ebrdoruesit si p\u00ebrgjigje. N\u00eb settings mund t\u00eb rregulloni nivelin e regjistrimit, log-et mund t\u00eb shikohen {ku u nxor\u00ebn nifi}\/nifi-1.9.2\/logs, aty ka gjithashtu parametrat failure\/success \u2014 duke u bazuar n\u00eb k\u00ebto parametra mund t\u00eb rregullohet procesi n\u00eb t\u00ebr\u00ebsi. Pra, n\u00eb rast t\u00eb suksessh\u00ebm t\u00eb p\u00ebrpunimit t\u00eb tekstit \u2014 do t\u00eb thirret nj\u00eb proces d\u00ebrgimi p\u00ebrgjigjeje p\u00ebr p\u00ebrdoruesin, ndryshe ne thjesht do ta regjistrojm\u00eb procesin e d\u00ebshtuar. <\/p>\n

<\/p>\n

\"Apache<\/p>\n

<\/p>\n

N\u00eb pronat e HandleHttpResponse nuk ka asgj\u00eb interesante p\u00ebrve\u00e7 statusit n\u00eb krijimin e suksessh\u00ebm t\u00eb p\u00ebrgjigjes. <\/p>\n

<\/p>\n

\"Apache<\/p>\n

<\/p>\n

Me p\u00ebrgjigjen e k\u00ebrk\u00ebs\u00ebs u m\u00ebsuam\u2014 le t\u00eb kalojm\u00eb tek marrja e skedarit dhe vendosja e tij n\u00eb serverin FTP. FetchFile \u2014 merr skedarin nga rruga e caktuar n\u00eb settings dhe e d\u00ebrgon at\u00eb n\u00eb procesin vijues. <\/p>\n

<\/p>\n

\"Apache<\/p>\n

<\/p>\n

Dhe katrori PutSftp vendos skedarin n\u00eb magazin\u00ebn e skedar\u00ebve. Parametrat e konfigurimit mund t\u00eb shihen m\u00eb posht\u00eb.<\/p>\n

<\/p>\n

\"Apache<\/p>\n

<\/p>\n

Kujdesi \u00ebsht\u00eb q\u00eb \u00e7do katror \u00ebsht\u00eb nj\u00eb proces i ve\u00e7ant\u00eb q\u00eb duhet t\u00eb aktivizohet. Ne shqyrtuam shembullin m\u00eb t\u00eb thjesht\u00eb q\u00eb nuk k\u00ebrkon ndonj\u00eb personalizim t\u00eb nd\u00ebrlikuar. Tani do t\u00eb shqyrtojm\u00eb nj\u00eb proces pak m\u00eb t\u00eb komplikuar, ku do t\u00eb shkruajm\u00eb pak n\u00eb Groovy. <\/p>\n

<\/p>\n

Shembulli m\u00eb i komplikuar<\/h3>\n

<\/p>\n

Sh\u00ebrbimi i transmetimit t\u00eb t\u00eb dh\u00ebnave p\u00ebr konsumatorin doli t\u00eb ishte pak m\u00eb i nd\u00ebrlikuar p\u00ebr shkak t\u00eb procesit t\u00eb modifikimit t\u00eb mesazhit SOAP. Procesi i p\u00ebrgjithsh\u00ebm paraqitet n\u00eb figur\u00ebn m\u00eb posht\u00eb.<\/p>\n

<\/p>\n

\"Apache<\/p>\n

<\/p>\n

K\u00ebtu ideja nuk \u00ebsht\u00eb shum\u00eb e komplikuar: mor\u00ebm nj\u00eb k\u00ebrkes\u00eb nga konsumatori p\u00ebr t\u00eb dh\u00ebna, d\u00ebrguam nj\u00eb p\u00ebrgjigje se mor\u00ebm mesazhin, aktivizuam procesin e marrjes s\u00eb skedarit t\u00eb p\u00ebrgjigjes, pastaj e redaktuam at\u00eb me nj\u00eb logjik\u00eb t\u00eb caktuar, pas s\u00eb cil\u00ebs e d\u00ebrguam skedarin p\u00ebr konsumatorin n\u00eb form\u00ebn e nj\u00eb mesazhi SOAP n\u00eb server. <\/p>\n

<\/p>\n

Nuk themi se nuk ka kuptim t\u00eb p\u00ebrshkruajm\u00eb p\u00ebrs\u00ebri katror\u00ebt q\u00eb pam\u00eb m\u00eb sip\u00ebr \u2014 le t\u00eb kalojm\u00eb drejtp\u00ebrdrejt n\u00eb t\u00eb rinjt\u00eb. N\u00ebse ju nevojitet t\u00eb redaktoni ndonj\u00eb skedar dhe katror\u00ebt e zakonsh\u00ebm si ReplaceText nuk jan\u00eb t\u00eb p\u00ebrshtatsh\u00ebm, do t'ju duhet t\u00eb shkruani skenarin tuaj. Kjo mund t\u00eb b\u00ebhet me ndihm\u00ebn e katrorit ExecuteGroogyScript. Cil\u00ebsimet e tij paraqiten m\u00eb posht\u00eb.<\/p>\n

<\/p>\n

\"Apache<\/p>\n

<\/p>\n

Jan\u00eb dy mund\u00ebsi p\u00ebr ngarkimin e skriptit n\u00eb k\u00ebt\u00eb katror. E para \u2014 \u00ebsht\u00eb p\u00ebrmes ngarkimit t\u00eb nj\u00eb skedari me skriptin. E dyta \u2014 duke e futur skriptin n\u00eb scriptBody. Sa di un\u00eb, katrori executeScript mb\u00ebshtet disa gjuh\u00eb programimi \u2014 nj\u00eb prej tyre \u00ebsht\u00eb groovy. Do t\u00eb zhg\u00ebnjej zhvilluesit e java \u2014 nuk \u00ebsht\u00eb e mundur t\u00eb shkruhen skripte n\u00eb k\u00ebto katror\u00eb me java. P\u00ebr ata q\u00eb e d\u00ebshirojn\u00eb shum\u00eb \u2014 duhet t\u00eb krijoni nj\u00eb katror t\u00eb personalizuar dhe ta ngjini at\u00eb n\u00eb sistemin NIFI. I gjith\u00eb ky operacion shoq\u00ebrohet me valle bastante t\u00eb gjata me bubullim\u00eb, me t\u00eb cilat nuk do t\u00eb merremi n\u00eb kuad\u00ebr t\u00eb k\u00ebtij artikulli. Kam zgjedhur gjuh\u00ebn groovy. M\u00eb posht\u00eb paraqitet nj\u00eb skript testues q\u00eb thjesht e p\u00ebrdit\u00ebson id-n\u00eb n\u00eb mesazhin SOAP n\u00eb m\u00ebnyr\u00eb inkrementale. \u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb theksohet. Ju merrni skedarin nga flowFile, e p\u00ebrdit\u00ebsoni at\u00eb, mos harroni se duhet, e p\u00ebrdit\u00ebsuar, ta vendosni p\u00ebrs\u00ebri aty. Gjithashtu, duhet t\u00eb theksohet se nuk jan\u00eb t\u00eb gjitha bibliotekat t\u00eb lidhura. Mund t\u00eb ndodh\u00eb q\u00eb do t'ju duhet t\u00eb importoni nj\u00eb nga librat. Nj\u00eb tjet\u00ebr disavantazh \u00ebsht\u00eb se skripti n\u00eb k\u00ebt\u00eb katror \u00ebsht\u00eb mjaft i v\u00ebshtir\u00eb p\u00ebr t'u debuguar. Ka nj\u00eb m\u00ebnyr\u00eb p\u00ebr t'u lidhur me JVM NIFI dhe p\u00ebr t\u00eb filluar procesin e debugimit. Personalmente, kam nisur nj\u00eb aplikacion lokal dhe kam imituar marrjen e skedarit nga seanca. Kam b\u00ebr\u00eb debugimin gjithashtu n\u00eb m\u00ebnyr\u00eb lokale. Gabimet q\u00eb shfaqen gjat\u00eb ngarkimit t\u00eb skriptit jan\u00eb mjaft t\u00eb lehta p\u00ebr t'u gjetur n\u00eb Google dhe shkruhen nga NIFI n\u00eb log.<\/p>\n

<\/p>\n

import org.apache.commons.io.IOUtils\nimport groovy.xml.XmlUtil\nimport java.nio.charset.*\nimport groovy.xml.StreamingMarkupBuilder\n\ndef flowFile = session.get()\nif (!flowFile) return\ntry {\n    flowFile = session.write(flowFile, { inputStream, outputStream ->\n        String result = IOUtils.toString(inputStream, \"UTF-8\");\n        def recordIn = new XmlSlurper().parseText(result)\n        def element = recordIn.depthFirst().find {\n            it.name() == 'id'\n        }\n\n        def newId = Integer.parseInt(element.toString()) + 1\n        def recordOut = new XmlSlurper().parseText(result)\n        recordOut.Body.ClientMessage.RequestMessage.RequestContent.content.MessagePrimaryContent.ResponseBody.id = newId\n\n        def res = new StreamingMarkupBuilder().bind { mkp.yield recordOut }.toString()\n        outputStream.write(res.getBytes(StandardCharsets.UTF_8))\n} as StreamCallback)\n     session.transfer(flowFile, REL_SUCCESS)\n}\ncatch(Exception e) {\n    log.error(\"Error during processing of validate.groovy\", e)\n    session.transfer(flowFile, REL_FAILURE)\n}<\/code><\/pre>\n
<\/p>\n
Kjo \u00ebsht\u00eb pik\u00ebrisht ku p\u00ebrfundon personalizimi i katrorit. Tani, skedari i p\u00ebrdit\u00ebsuar kalon n\u00eb katrorin q\u00eb merret me d\u00ebrgimin e skedarit n\u00eb server. M\u00eb posht\u00eb jan\u00eb paraqitur konfigurimet e k\u00ebtij katrori.<\/p>\n
<\/p>\n
\"Apache<\/p>\n
<\/p>\n
P\u00ebrshkruajm\u00eb metod\u00ebn me t\u00eb cil\u00ebn do t\u00eb d\u00ebrgohet mesazhi SOAP. Shkruajm\u00eb se ku. M\u00eb pas, duhet t\u00eb specifikojm\u00eb se \u00ebsht\u00eb pik\u00ebrisht SOAP.<\/p>\n
<\/p>\n
\"Apache<\/p>\n
<\/p>\n
Shtojm\u00eb disa pronar\u00eb si host dhe veprimin (soapAction). Ruajm\u00eb, kontrollojm\u00eb. M\u00eb shum\u00eb detaje p\u00ebr d\u00ebrgimin e mesazheve SOAP mund t\u00eb shihni. k\u00ebtu<\/a><\/noindex><\/p>\n
<\/p>\n
Ne shqyrtuam disa m\u00ebnyra se si p\u00ebrdoren proceset NIFI. Si nd\u00ebrveprojn\u00eb ato dhe \u00e7far\u00eb dobie reale sjellin. Shembujt e shqyrtuar jan\u00eb testues dhe pak ndryshe nga ato q\u00eb ndodhin n\u00eb praktik\u00eb. Shpresoj q\u00eb ky artikull t\u00eb jet\u00eb disi i dobish\u00ebm p\u00ebr zhvilluesit. Faleminderit p\u00ebr v\u00ebmendjen. N\u00ebse keni ndonj\u00eb pyetje - shkruani. Do t\u00eb p\u00ebrpiqem t\u00eb p\u00ebrgjigjem.<\/p>\n
Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0422\u0430\u043a \u043f\u043e\u043b\u0443\u0447\u0438\u043b\u043e\u0441\u044c, \u0447\u0442\u043e \u043d\u0430 \u043c\u043e\u0435\u043c \u0442\u0435\u043a\u0443\u0449\u0435\u043c \u043c\u0435\u0441\u0442\u0435 \u0440\u0430\u0431\u043e\u0442\u044b \u043c\u043d\u0435 \u043f\u0440\u0438\u0448\u043b\u043e\u0441\u044c \u043f\u043e\u0437\u043d\u0430\u043a\u043e\u043c\u0438\u0442\u044c\u0441\u044f \u0441 \u0434\u0430\u043d\u043d\u043e\u0439 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0435\u0439. \u041d\u0430\u0447\u043d\u0443 \u0441 \u043d\u0435\u0431\u043e\u043b\u044c\u0448\u043e\u0439 \u043f\u0440\u0435\u0434\u044b\u0441\u0442\u043e\u0440\u0438\u0438. \u041d\u0430 \u043e\u0447\u0435\u0440\u0435\u0434\u043d\u043e\u043c \u043c\u0438\u0442\u0438\u043d\u0433\u0435, \u043d\u0430\u0448\u0435\u0439 \u043a\u043e\u043c\u0430\u043d\u0434\u0435 \u0441\u043a\u0430\u0437\u0430\u043b\u0438, \u0447\u0442\u043e \u043d\u0443\u0436\u043d\u043e \u0441\u043e\u0437\u0434\u0430\u0442\u044c \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0446\u0438\u044e \u0441 \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u043e\u0439. \u041f\u043e\u0434 \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0446\u0438\u0435\u0439 \u043f\u043e\u0434\u0440\u0430\u0437\u0443\u043c\u0435\u0432\u0430\u043b\u043e\u0441\u044c, \u0447\u0442\u043e \u044d\u0442\u0430 \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u0430\u044f \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0431\u0443\u0434\u0435\u0442 \u043d\u0430\u043c \u0441\u043b\u0430\u0442\u044c \u0437\u0430\u043f\u0440\u043e\u0441\u044b \u0447\u0435\u0440\u0435\u0437 HTTP \u043d\u0430 \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u043d\u044b\u0439 \u0435\u043d\u0434\u043f\u043e\u0438\u043d\u0442, \u0430 \u043c\u044b, \u043a\u0430\u043a \u044d\u0442\u043e \u043d\u0438 \u0441\u0442\u0440\u0430\u043d\u043d\u043e, \u0441\u043b\u0430\u0442\u044c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28196,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-37567","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-novosti-interneta"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Apache NIFI \u2014 Nj\u00eb p\u00ebrmbledhje e mund\u00ebsive n\u00eb praktik\u00eb | ProHoster","description":"Hyrje K\u00ebshtu ndodhi q\u00eb n\u00eb vendin tim aktual t\u00eb pun\u00ebs, m\u00eb duhet t\u00eb njihem me k\u00ebt\u00eb teknologji. T\u00eb fillojm\u00eb me nj\u00eb histori t\u00eb vog\u00ebl. N\u00eb nj\u00eb takim, ekipi yn\u00eb u informua se ne duhet t\u00eb krijojm\u00eb nj\u00eb integrim me nj\u00eb sistem t\u00eb njohur. Integrimi n\u00ebnkuptonte se ky sistem i njohur do t\u00eb na d\u00ebrgonte k\u00ebrkesa p\u00ebrmes HTTP n\u00eb nj\u00eb endpoint t\u00eb caktuar, dhe ne, si\u00e7 \u00ebsht\u00eb e \u00e7uditshme, do t\u00eb d\u00ebrgonim.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/apache-nifi-kratkij-obzor-vozmozhnostej-na-praktike","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47Apache NIFI \u2014 \u041a\u0440\u0430\u0442\u043a\u0438\u0439 \u043e\u0431\u0437\u043e\u0440 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0435\u0439 \u043d\u0430 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0435 | ProHoster","og:description":"\u0412\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0422\u0430\u043a \u043f\u043e\u043b\u0443\u0447\u0438\u043b\u043e\u0441\u044c, \u0447\u0442\u043e \u043d\u0430 \u043c\u043e\u0435\u043c \u0442\u0435\u043a\u0443\u0449\u0435\u043c \u043c\u0435\u0441\u0442\u0435 \u0440\u0430\u0431\u043e\u0442\u044b \u043c\u043d\u0435 \u043f\u0440\u0438\u0448\u043b\u043e\u0441\u044c \u043f\u043e\u0437\u043d\u0430\u043a\u043e\u043c\u0438\u0442\u044c\u0441\u044f \u0441 \u0434\u0430\u043d\u043d\u043e\u0439 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0435\u0439. \u041d\u0430\u0447\u043d\u0443 \u0441 \u043d\u0435\u0431\u043e\u043b\u044c\u0448\u043e\u0439 \u043f\u0440\u0435\u0434\u044b\u0441\u0442\u043e\u0440\u0438\u0438. \u041d\u0430 \u043e\u0447\u0435\u0440\u0435\u0434\u043d\u043e\u043c \u043c\u0438\u0442\u0438\u043d\u0433\u0435, \u043d\u0430\u0448\u0435\u0439 \u043a\u043e\u043c\u0430\u043d\u0434\u0435 \u0441\u043a\u0430\u0437\u0430\u043b\u0438, \u0447\u0442\u043e \u043d\u0443\u0436\u043d\u043e \u0441\u043e\u0437\u0434\u0430\u0442\u044c \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0446\u0438\u044e \u0441 \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u043e\u0439. \u041f\u043e\u0434 \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0446\u0438\u0435\u0439 \u043f\u043e\u0434\u0440\u0430\u0437\u0443\u043c\u0435\u0432\u0430\u043b\u043e\u0441\u044c, \u0447\u0442\u043e \u044d\u0442\u0430 \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u0430\u044f \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0431\u0443\u0434\u0435\u0442 \u043d\u0430\u043c \u0441\u043b\u0430\u0442\u044c \u0437\u0430\u043f\u0440\u043e\u0441\u044b \u0447\u0435\u0440\u0435\u0437 HTTP \u043d\u0430 \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u043d\u044b\u0439 \u0435\u043d\u0434\u043f\u043e\u0438\u043d\u0442, \u0430 \u043c\u044b, \u043a\u0430\u043a \u044d\u0442\u043e \u043d\u0438 \u0441\u0442\u0440\u0430\u043d\u043d\u043e, \u0441\u043b\u0430\u0442\u044c","og:url":"https:\/\/prohoster.info\/sq\/blog\/novosti-interneta\/apache-nifi-kratkij-obzor-vozmozhnostej-na-praktike","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:18:22+00:00","article:modified_time":"2019-10-31T19:18:22+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37567","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-23 18:24:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:24:24","updated":"2026-01-23 18:24:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37567","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=37567"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37567\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/28196"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=37567"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=37567"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=37567"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}