The document describes the configuration details of a scheduler that runs jobs to export social media data from various sources to a universal profile database. It outlines the deployment environment, database connections, configurable jobs, and mysql tables used to track scheduled jobs and export status. The system job checks the job schedule table every 20 minutes to identify new or updated jobs to run. Export jobs move data from partner databases to the universal profile based on modified timestamps and client/account ids.
Temporal Tables are a great MariaDB feature that allows us to query past data, seeing how data were at a certain point in time, or how they changed over a given period. The slides illustrate the feature itself, how to use it, what can be done with it, and a set of opinionated good practices. Federico Razzoli gave this talk at MariaDB Server Fest 2020.
Temporal Tables are a great MariaDB feature that allows us to query past data, seeing how data were at a certain point in time, or how they changed over a given period. The slides illustrate the feature itself, how to use it, what can be done with it, and a set of opinionated good practices. Federico Razzoli gave this talk at MariaDB Server Fest 2020.
EXPERIMENTAL INVESTIGATION ON THERMAL PERFORMANCE OF POROUS RADIANT BURNER AN...BIBHUTI BHUSAN SAMANTARAY
This paper presents the heat transfer characteristics of a
self-aspirating porous radiant burner (SAPRB) that operates
on the basis of an effective energy conversion method between
flowing gas enthalpy and thermal radiation. The temperature
field at various flame zones was measured experimentally by
the help of both FLUKE IR camera and K-type thermocouples.
The experimental setup consisted of a two layered domestic
cooking burner, a flexible test stand attached with six K-type
thermocouples at different positions, IR camera, LPG setup
and a hot wire anemometer. The two layered SAPRB consisted
of a combustion zone and a preheating zone. Combustion zone
was formed with high porosity, highly radiating porous
matrix, and the preheating zone consisted of low porosity
matrix. Time dependent temperature history from
thermocouples at various flame zones were acquired by using
a data acquisition system and the temperature profiles were
analyzed in the ZAILA application software environments. In
the other hand the IR graphs were captured by FLUKE IR
camera and the thermographs were analyzed in the
SMARTView software environments. The experimental results
revealed that the homogeneous porous media, in addition to
its convective heat exchange with the gas, might absorb, emit,
and scatter thermal radiation. The rate of heat transfer was
more at the center of the burner where a combined effect of
both convection & radiation might be realized. The maximum
thermal efficiency was found to be 64% which was having a
good agreement with the previous data in the open literature.
Pongamia Pinnata is the scientific name of Karanja. It is a medium sized tree that is plentily found alloverOdisha. There are a lot of research is going on regarding production of Biodiesel from Karanja oil but the main objective of the paper is the production and implementation of Glycerol from Karanja oil. Alcohol glycerol, a clear, colorless, viscous, sweet-tasting liquid belonging to the family of organic compounds; molecular formula HOCH2CHOHCH2OH. In this experiment we have produced Biodiesel as well as Glycerol as a byproduct but we have focused mainly on the formation of the Glycerol and its application. So in a different view point,if the production of value added glycerol can be increased within the same cost of biodiesel production, overall cost of biodiesel can be reduced to an optimum level. The effective utilization of crude glycerol will contribute to the viability of biodiesel. In this experiment, we have taken non edible Karanja oil for preparation of Glycerol by transesterification of crude oil with methanol in presence of NaOH/KOH as catalyst and yielded of approximately 11% (w/w) glycerol.
EXPERIMENTAL INVESTIGATION ON THERMAL PERFORMANCE OF POROUS RADIANT BURNER AN...BIBHUTI BHUSAN SAMANTARAY
This paper presents the heat transfer characteristics of a
self-aspirating porous radiant burner (SAPRB) that operates
on the basis of an effective energy conversion method between
flowing gas enthalpy and thermal radiation. The temperature
field at various flame zones was measured experimentally by
the help of both FLUKE IR camera and K-type thermocouples.
The experimental setup consisted of a two layered domestic
cooking burner, a flexible test stand attached with six K-type
thermocouples at different positions, IR camera, LPG setup
and a hot wire anemometer. The two layered SAPRB consisted
of a combustion zone and a preheating zone. Combustion zone
was formed with high porosity, highly radiating porous
matrix, and the preheating zone consisted of low porosity
matrix. Time dependent temperature history from
thermocouples at various flame zones were acquired by using
a data acquisition system and the temperature profiles were
analyzed in the ZAILA application software environments. In
the other hand the IR graphs were captured by FLUKE IR
camera and the thermographs were analyzed in the
SMARTView software environments. The experimental results
revealed that the homogeneous porous media, in addition to
its convective heat exchange with the gas, might absorb, emit,
and scatter thermal radiation. The rate of heat transfer was
more at the center of the burner where a combined effect of
both convection & radiation might be realized. The maximum
thermal efficiency was found to be 64% which was having a
good agreement with the previous data in the open literature.
Pongamia Pinnata is the scientific name of Karanja. It is a medium sized tree that is plentily found alloverOdisha. There are a lot of research is going on regarding production of Biodiesel from Karanja oil but the main objective of the paper is the production and implementation of Glycerol from Karanja oil. Alcohol glycerol, a clear, colorless, viscous, sweet-tasting liquid belonging to the family of organic compounds; molecular formula HOCH2CHOHCH2OH. In this experiment we have produced Biodiesel as well as Glycerol as a byproduct but we have focused mainly on the formation of the Glycerol and its application. So in a different view point,if the production of value added glycerol can be increased within the same cost of biodiesel production, overall cost of biodiesel can be reduced to an optimum level. The effective utilization of crude glycerol will contribute to the viability of biodiesel. In this experiment, we have taken non edible Karanja oil for preparation of Glycerol by transesterification of crude oil with methanol in presence of NaOH/KOH as catalyst and yielded of approximately 11% (w/w) glycerol.
The user synchronization is normally made via sync_all_dns script that synchronize users information from LDAP to the EMPINST.EMPLOYEE table. If you synchronize a field such as “telephone number” when a user edits the value in IBM Connections at next run of sync_all_dns script the change is lost. To avoid this problem you must setup the synchronization from EMPLOYEE table to LDAP by using the script process_draft_updates.sh
New Features
● Developer and SQL Features
● DBA and Administration
● Replication
● Performance
By Amit Kapila at India PostgreSQL UserGroup Meetup, Bangalore at InMobi.
http://technology.inmobi.com/events/india-postgresql-usergroup-meetup-bangalore
MariaDB 10.4 became General Available (GA = ready for production) this summer. So it is time to look at the new Features in MariaDB 10.4. After a short intro about history we look for the reason of broad usage of MariaDB nowadays. Most important improvements where in User Authentication, InnoDB improvements, and Optimizer enhancements. A completely New Feature is Application-Time Period Tables. Backup got a new Locking behaviour so LVM snapshots are possible and officially supported now. And last but not least MariaDB 10.4 comes with Galera 4.
Android Lollipop internals and inferiority complex droidcon.hr 2015 Aleksander Piotrowski
Presentation from droidcon Zagreb 2015
While going through JobScheduler internals try to answer the following question: How big is the gap between us and rockstar developers from Google or Square
Peeking into the Black Hole Called PL/PGSQL - the New PL Profiler / Jan Wieck...Ontico
The new PL profiler allows you to easily get through the dark barrier, PL/pgSQL puts between tools like pgbadger and the queries, you are looking for.
Query and schema tuning is tough enough by itself. But queries, buried many call levels deep in PL/pgSQL functions, make it torture. The reason is that the default monitoring tools like logs, pg_stat_activity and pg_stat_statements cannot penetrate into PL/pgSQL. All they report is that your query calling function X is slow. That is useful if function X has 20 lines of simple code. Not so useful if it calls other functions and the actual problem query is many call levels down in a dungeon of 100,000 lines of PL code.
Learn from the original author of PL/pgSQL and current maintainer of the plprofiler extension how you can easily analyze, what is going on inside your PL code.
(2) cpp abstractions abstraction_and_encapsulationNico Ludwig
This presentation comes with many additional notes (pdf): http://de.slideshare.net/nicolayludwig/2-cpp-abstractions-abstractionandencapsulation-38533809
Check out these exercises: http://de.slideshare.net/nicolayludwig/2-cpp-abstractions-abstractionandencapsulationexercises-38533848
- Concepts of Object-Orientation: Abstraction and Encapsulation
- Abstracted Types with Member Functions
- Constructors and default Constructors
- Restricting Access to Members
- Encapsulation with Classes
- Inline Member Functions
- Naming Conventions
1. Scheduler Architecture
1. Deployment details :-
For a QA system the scheduler instance is running on DEV1 server box.
■ Deployment Path - /mnt1/scheduler/
■ Start script location - /mnt1/scheduler/bin/
■ Log File Configuration - /mnt1/scheduler/logconfig
■ Spring Configuration - /mnt1/scheduler/spring
■ Log File location - /mnt1/logs/scheduler2.0-global-logs.log
■ Quartz Database - All the Quartz related table are created under the following details.
● DB Host = DEV1
● DB Name = SCHEDULER_GRL:3306
● DB user = sprmys
● DB Password = R1k1rP5
● Quartz Tables = QRTZ*
■ Job Details Database - The configured jobs and the last run details are captured in the
following tables
● DB Host = QA2
● DB Name = SPR_GRL
● SCHEDULABLE_JOB_TBL = configured jobs
● CLIENT_UNIVERSAL_PROFILE_EXPORT_TBL = details last successful runs.
■ Failure Details - At times the Scheduler, Job or the Trigger may fail, these details are captured
in the mongo DB.
● Mongo Host = ec2-107-22-29-36.compute-1.amazonaws.com
● DB Name = SPR_GLOBAL
● Collection Names :-
○ failedJobDetail - Captures the failed job details
○ failedSchedulerDetail - Captures the failed scheduler details.
○ triggerMissFireDetail - Captures the missed trigger details.
2. 2. System Job Details :-
Sprinklr has been pre-configured with system job which runs every 5 minutes to check
the “SCHEDULABLE_JOB_TBL” changes in the SPR_GRL database.
If this time expression to run every five minutes needs to be changed the following entry needs to
be made in the “spring-quartz.xml” file (maked in bold). Adding the following entry would ensure that the
system job is scheduled to run every 20 mins as opposed to the 5 minutes it has been configured to run.
Restart the scheduler instance after the change has been made to reflect the same.
<bean id="sprScheduler" class="com.spr.scheduler.QuartzSchedulerImpl">
<property name="scheduler">
<ref bean="schedulerFactoryBean"/>
</property>
<property name="jobBasePackageName">
<value>com.spr.jobs</value>
</property>
<property name="overrideSystemJobMap">
<map>
<entry key="com.spr.jobs.system.JobSchedulerJob">
<!-- scheduled the job to run once a century at every 20 mins -->
<value>* 0/20 * * * ?</value>
</entry>
</map>
</property>
<ignored rest of the properties/>
3. 3. Configurable Jobs :-
The following list of Jobs can be configured in the scheduler.
1. com.spr.jobs.export.twitter.ExportTwitterClientProfileToUniversalProfileJob
Exports the data from “PROFILE_TBL” based on the “MODIFIED_TM”, “CLIENT_ID”, “ACCOUNT_ID”
and the “PARTNER_ID” to then “universalProfile” collection.
2. com.spr.jobs.export.twitter.ExportTwitterConversationToUniversalProfileJob
Exports the data from “ACCOUNT_TWEET_TBL” based on
the “CREATED_TM”, “CLIENT_ID”, “ACCOUNT_ID” and the “PARTNER_ID” to then “conversation”
collection.
3. com.spr.jobs.export.twitter.ExportTwitterFollowerAndFollowingDetailsJob
Export the data from “ACCOUNT_FFUF_TBL” based on
the “MODIFIED_TM”, “CLIENT_ID”, “ACCOUNT_ID” and the “PARTNER_ID” to the “universalProfile”
collection.
4. com.spr.jobs.export.facebook.ExportFacebookClientProfileToUniversalProfileJob
Export the data from “FB_PROFILE_TBL” based on the “MODIFIED_TM”, “CLIENT_ID”, “ACCOUNT_ID”
and the “PARTNER_ID” to the universalProfile” collection.
5. com.spr.jobs.export.facebook.ExportFacebookCommentsToUniversalProfileJob
Exports the data from “FB_ACCOUNT_COMMENTS_TBL” based on
the “CREATED_TM”, “CLIENT_ID”, “ACCOUNT_ID” and the “PARTNER_ID” to the “conversation”
collection.
6. com.spr.jobs.export.facebook.ExportFacebookConversationToUniversalProfileJob
Exports the data from “FB_INBOX_STREAM_TBL” based on
the “CREATED_TM”, “CLIENT_ID”, “ACCOUNT_ID” and the “PARTNER_ID” to the “conversation”
collection.
4. 4. MySql Tables :-
● SCHEDULABLE_JOB_TBL - This table captures the job which need to be scheduled
in the scheduler. The JOB_CLASS, PARTNER_ID, CLIENT_ID and the CLIENT_ID form the
uniqueness.
○ SCHEDULABLE_JOB_TBL_ID - The primary key
○ JOB_CLASS_NAME - The name of job class, as defined above. This is the business
logic to executes.
○ PARTNER_ID - The Partner Id
○ CLIENT_ID - The Client Id
○ ACCOUNT_ID - The Account Id
○ JOB_DATA - Any additional data as a JSON string to be made available to job during its
execution.
○ CRON_EXPRESSION - The Cron Expression which defines the run intervals.
○ IS_SCHEDULED - Boolean to define is the job is scheduled on the scheduler. This
column is used by the System Job and is internal to the scheduler.
○ IS_ENABLED - if set to true, would enable the job in the scheduler to run on the
scheduler cron time, if set to false, would disable the enabled job from the scheduler, and
this job will not be qualified for any further runs.
○ CREATED_TM - The time at which this record was created
○ MODIFIED_TM - The time at which this record was updated.
○ DEL_FLG - If set to true, would delete the job from the scheduler along with its
associated triggers. To qualify this job to run again set the flag to false.
○ SCHEDULE_KEY - The unique key which identifies the job. This column is used by the
System Job and is internal to the scheduler.
● CLIENT_UNIVERSAL_PROFILE_EXPORT_TBL - This table captures the last run
details for the job configured. This table is internal to the jobs and should be used only for look-
ups.
○ PARTNER_ID - The Partner id
○ CLIENT_ID - The Client Id
○ ACCOUNT_ID - The account Id
○ LAST_EXPORT_DATE - The date till which the job did its last export.
○ SN_TYPE - The Social Network Type
○ EXPORT_TYPE - The Export type, can be one of Profile, Conversation or Comment