catalog | Made with Manubot catalog | Dataset library

Went with option 2. The Redshift Copy/Load process writes csv with manifest to S3 in any case so duplicating that is pointless.

Regarding the Questions:

1. N/A

2. Job Bookmarking does work. There is some gotchas though - ensure Connections both to RDS and Redshift are present in Glue Pyspark job, IAM self ref rules are in place and to identify a row that is unique [I chose the primary key of underlying table as an additional column in my materialized view] to use as the bookmark.

3. Using the primary key of core table may buy efficiencies in pruning materialized views during maintenance cycles. Just retrieve latest bookmark from cli using aws glue get-job-bookmark --job-name yourjobname and then just that in the where clause of the mv as where id >= idinbookmark

   conn = glueContext.extract_jdbc_conf("yourGlueCatalogdBConnection") connection_options_source = { "url": conn['url'] + "/yourdB", "dbtable": "table in dB", "user": conn['user'], "password": conn['password'], "jobBookmarkKeys":["unique identifier from source table"], "jobBookmarkKeysSortOrder":"asc"}

datasource0 = glueContext.create_dynamic_frame.from_options(connection_type="postgresql", connection_options=connection_options_source, transformation_ctx="datasource0")

That's all, folks

I would recommend using /action:Script (see here) to see which actions it will perform, most likely this will give you some clue as to which flags should be set/cleared.

-- Edit According to this old answer you can disable deploying the database properties when designing the .dacpac.
If you want to override this behaviour when publishing the .dacpac, you should probably use the ScriptDatabaseOptions property - see the whole list of switches here.

My question is, is it correct to specifiy multiple XSD file implementing the same namespace with different xsd structures ?

Yes, that is a valid use of XML schema. A schema does not have to be represented by a single XSD file. Please see https://www.w3.org/TR/xmlschema-0/#SchemaInMultDocs and https://www.w3.org/TR/xmlschema-0/#import

You may also find this thread helpful: What's the difference between xsd:include and xsd:import?

I would start with running sp_who2 on the database server to see if sqlpackage has made a connection to it, and if it's blocking on the server somewhere.

If so, you can further investigate with the SQL Server Profiler (can be found in the Tools menu of SQL Server Management Studio)

It looks like you've got PHP that's embedded in your JavaScript program, and you want some sort of live updating system to change the button statuses when the data changes. When a client requests the page from the server, the server will execute the PHP code and then insert the results from the echo statements into your code. This means that all the client sees is the result of the PHP execution, like so:

SaxonJS.getResource() is asynchronous and returns a Promise; I think you have supplied this Promise to SaxonJS.XPath.Evaluate(), which is treating it as a general Javascript object.

You need something like

Ok, the signature container is embedded correctly.

But there are issues with the signature container itself:

• Both in the SignedData.digestAlgorithms collection and in the SignerInfo.digestAlgorithm value you have used the OID of SHA1withRSA, but that is a full signature algorithm, not the mere digest algorithm SHA1 expected there.

• Then the SHA1 hash of the signed bytes is BB78A402F7A537A34D6892B83881266501A691A8 but the hash you signed is 90E28B8A0D8E48691DAFE2BA10A4761FFFDCCD3D. This might be because you hash buffer2 and

  buffer2 has empty contents data (/Contents <>)

  The hex string delimiters '<' and '>' also belong to the contents value and, therefore, must also be removed in buffer2.

Furthermore, your signature is very weak:

• It uses SHA1 as hash algorithm. SHA1 meanwhile has been recognized as too weak a hash algorithm for document signatures.
• It doesn't use signed attributes, neither the ESS signing certificate nor the algorithm identifier protection attribute. Many validation policies require such special attributes.

From what is can see, it should work properly. What log do you have on execution?

waitForSucceeded() is a closure, aka anopnymous function. You can find some documentation/ detail here: https://www.php.net/manual/fr/functions.anonymous.php https://www.php.net/manual/fr/class.closure.php

So here is what the closure do:

This is how Start-Process command was basically created. -PassThru switch redirects the output to an object ($sqlpackagepublish in this case). More on Start-Process here: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/start-process?view=powershell-5.1

There are few solutions.

1. Remove a -PassThru parameter and read files' content as you are doing it right now
2. Do it harder, but more robust .NET'y way: