MiNiFi

Apache NiFi/MiNiFi - A subproject to collect data where it originates(source).

Comments

Post a Comment

Popular posts from this blog

Okta

Okta is Cloud based Identity and Access Management platform. Below  are some notes from a whitepaper published on Okta website.  Okta can be used as foundation for implementing Zero Trust within organizations.  Zero Trust is a security framework developed by Forrester Research.   Zero Trust => never trust, always verify Zero Trust framework evolved later  into ZTX ( Zero Trust Extended Ecosystem ) . The focus has shifted from network perimeter to  access ( who is accessing the system ). The focus has shifted to Identity and Access Control.  There are four stages of Zero Trust implementation: Fragmented Identity Unified IAM Contextual Access : Context based access policies Adaptive Workforce : Risk based access policies, continuous and adaptive authn and authz Services Offered By OKta Okta Universal Directory Okta SSO  Okta Advanced Server Access Okta Adaptive MFA Okta also integrates with number of vendors in security ecosystem.  That...
Read more

UNIX/LINUX

1. Use Ctrl+D for specifying EOF for stdin. 2. Removing the files returned by svn status command. svn status | awk '{cmd = "rm " $2; system(cmd)}' 3. To find the Linux distribution on the machine more /etc/*-release 4.  top, htop, iotop,sysstat  for seeing the system usage. 5.  jstack   for seeing the threads inside a java process 6. In LDAP access log , to print all the lines which has etimes greater than 10 ms and also print next line if it has "SRCH" into it, use following command awk -F= '/etime/ && $7>0.02000 {print FNR; print;getline; print FNR;if (match($0,"SRCH")) {print}}'  access 6.1  To list all the lines which have etime > 1000 ms   awk -F"etime=" '$2>1000 {print }' access 7.  In LDAP access log, print the previous line and the line where etimes greater than 10 ms. awk -F= '/etime/ && $7>0.01000 { print line;print;} {line=$0}'  access 8. Su...
Read more

Transactions in HIVE

Full ACID  semantics at row level is supported since HIVE  0.13.  Earlier it was only supported at partition level.   Atomicity: Entire operation is single operation. Either entire operation happens or none. Consistency: Once an operation is completed, every subsequent operations sees the same result of it.  Isolation: One user operation does not impact another user.  Durability: Once operation is done ..its result remains thereafter. At present isolation is only at snapshot level. There are following isolation levels in various DBMS: Snapshot: The snapshot of data at the beginning of  transaction will be visible to through out the transaction. Whatever is happening in other transaction will never be seen by this transaction.  Dirty Read: Uncommitted updates from other transactions can be seen. Read Committed: Only updates which are committed at the time of read will be seen by this transaction. Repeatable Read: Read lock on data being read a...
Read more