Best practise for data dump 'entry point' in DB processing chain - PostgreSQL
I need to implement a process chain to transform and analyze potentially large sets of data, inserted both programmatically and manually (e.g. CSVs). In either way, the input data is standardized in terms of columns and datatypes. New data-sets are added regularly.
Once inserted, however, the data needs to be transformed and aggregated (spatially -> PostGIS) into different table structures (columns & datatypes) to then be analyzed extensively and distributed among several related tables where they will be stored (appended) as results. The initially inserted data will be obsolete once processed.
l need to define an 'entry point' to this process chain, and I am not sure which way to go; I intend to have users generally to not work on the base relations themselves (thus working on Views, while 'working on' generally refers to select and export), and I'd like to not have an 'empty' (truncated each time) physical table sitting in the DB for this if not necessary.
The 'entry point' should ideally be accessible via simple INSERT or COPY/copy commands; I could possibly set up fdw connections to directly query the data without an 'entry point', but I'm not sure how I could make that available universally and mostly automated (I don't want users to need to set up the fdw server connection each time; if this can be automated, feel free to add solutions accordingly).
How would I define an 'entry point' to dump data for further processing, where the input data structure differs substantially from the subsequent tables in the chain and has to be deleted after import or is only transitional?
database-design table postgresql-10
asked 10 mins ago
t.ryt.ry
11
New contributor
t.ry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I need to implement a process chain to transform and analyze potentially large sets of data, inserted both programmatically and manually (e.g. CSVs). In either way, the input data is standardized in terms of columns and datatypes. New data-sets are added regularly.
Once inserted, however, the data needs to be transformed and aggregated (spatially -> PostGIS) into different table structures (columns & datatypes) to then be analyzed extensively and distributed among several related tables where they will be stored (appended) as results. The initially inserted data will be obsolete once processed.
l need to define an 'entry point' to this process chain, and I am not sure which way to go; I intend to have users generally to not work on the base relations themselves (thus working on Views, while 'working on' generally refers to select and export), and I'd like to not have an 'empty' (truncated each time) physical table sitting in the DB for this if not necessary.
The 'entry point' should ideally be accessible via simple INSERT or COPY/copy commands; I could possibly set up fdw connections to directly query the data without an 'entry point', but I'm not sure how I could make that available universally and mostly automated (I don't want users to need to set up the fdw server connection each time; if this can be automated, feel free to add solutions accordingly).
How would I define an 'entry point' to dump data for further processing, where the input data structure differs substantially from the subsequent tables in the chain and has to be deleted after import or is only transitional?
database-design table postgresql-10
asked 10 mins ago
t.ryt.ry
11
New contributor
t.ry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I do realize that this might better be handled externally/application-wise, but I am bound to do it this way.
– t.ry
9 mins ago
add a comment |
I need to implement a process chain to transform and analyze potentially large sets of data, inserted both programmatically and manually (e.g. CSVs). In either way, the input data is standardized in terms of columns and datatypes. New data-sets are added regularly.
Once inserted, however, the data needs to be transformed and aggregated (spatially -> PostGIS) into different table structures (columns & datatypes) to then be analyzed extensively and distributed among several related tables where they will be stored (appended) as results. The initially inserted data will be obsolete once processed.
l need to define an 'entry point' to this process chain, and I am not sure which way to go; I intend to have users generally to not work on the base relations themselves (thus working on Views, while 'working on' generally refers to select and export), and I'd like to not have an 'empty' (truncated each time) physical table sitting in the DB for this if not necessary.
The 'entry point' should ideally be accessible via simple INSERT or COPY/copy commands; I could possibly set up fdw connections to directly query the data without an 'entry point', but I'm not sure how I could make that available universally and mostly automated (I don't want users to need to set up the fdw server connection each time; if this can be automated, feel free to add solutions accordingly).
How would I define an 'entry point' to dump data for further processing, where the input data structure differs substantially from the subsequent tables in the chain and has to be deleted after import or is only transitional?
database-design table postgresql-10
asked 10 mins ago
t.ryt.ry
11
New contributor
t.ry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I need to implement a process chain to transform and analyze potentially large sets of data, inserted both programmatically and manually (e.g. CSVs). In either way, the input data is standardized in terms of columns and datatypes. New data-sets are added regularly.
Once inserted, however, the data needs to be transformed and aggregated (spatially -> PostGIS) into different table structures (columns & datatypes) to then be analyzed extensively and distributed among several related tables where they will be stored (appended) as results. The initially inserted data will be obsolete once processed.
l need to define an 'entry point' to this process chain, and I am not sure which way to go; I intend to have users generally to not work on the base relations themselves (thus working on Views, while 'working on' generally refers to select and export), and I'd like to not have an 'empty' (truncated each time) physical table sitting in the DB for this if not necessary.
The 'entry point' should ideally be accessible via simple INSERT or COPY/copy commands; I could possibly set up fdw connections to directly query the data without an 'entry point', but I'm not sure how I could make that available universally and mostly automated (I don't want users to need to set up the fdw server connection each time; if this can be automated, feel free to add solutions accordingly).
How would I define an 'entry point' to dump data for further processing, where the input data structure differs substantially from the subsequent tables in the chain and has to be deleted after import or is only transitional?
database-design table postgresql-10
database-design table postgresql-10
asked 10 mins ago
t.ryt.ry
11
New contributor
t.ry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 10 mins ago
t.ryt.ry
11
New contributor
t.ry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 4 mins ago
t.ry
asked 10 mins ago
t.ryt.ry
11
New contributor
t.ry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 10 mins ago
t.ryt.ry
11
asked 10 mins ago
t.ryt.ry
11
11
New contributor
t.ry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
t.ry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
t.ry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I do realize that this might better be handled externally/application-wise, but I am bound to do it this way.
– t.ry
9 mins ago
add a comment |
I do realize that this might better be handled externally/application-wise, but I am bound to do it this way.
– t.ry
9 mins ago
I do realize that this might better be handled externally/application-wise, but I am bound to do it this way.
– t.ry
9 mins ago
I do realize that this might better be handled externally/application-wise, but I am bound to do it this way.
– t.ry
9 mins ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
t.ry is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f227008%2fbest-practise-for-data-dump-entry-point-in-db-processing-chain-postgresql%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
t.ry is a new contributor. Be nice, and check out our Code of Conduct.
t.ry is a new contributor. Be nice, and check out our Code of Conduct.
t.ry is a new contributor. Be nice, and check out our Code of Conduct.
t.ry is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f227008%2fbest-practise-for-data-dump-entry-point-in-db-processing-chain-postgresql%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I do realize that this might better be handled externally/application-wise, but I am bound to do it this way.
– t.ry
9 mins ago