Lirong Jian created HAWQ-122: -------------------------------- Summary: FILESPACE URL in pg_filespace_entry is confusing Key: HAWQ-122 URL: https://issues.apache.org/jira/browse/HAWQ-122 Project: Apache HAWQ Issue Type: Improvement Components: Storage Reporter: Lirong Jian Assignee: Lei Chang
postgres=# SELECT * FROM pg_filespace_entry; fsefsoid | fsedbid | fselocation ----------+---------+------------------------------ 16384 | 0 | hdfs://Lirong-MBP:9000/gpsql (1 row) postgres=# CREATE FILESPACE fs_1 ON HDFS ( postgres(# 'Lirong-MBP:9000/hawq/fs_1'); CREATE FILESPACE postgres=# CREATE FILESPACE fs_2 ON HDFS ( 'Lirong-MBP:9000/hawq/fs_2') WITH (NUMREPLICA=2); CREATE FILESPACE postgres=# CREATE FILESPACE fs_3 ON HDFS ( 'Lirong-MBP:9000/hawq/fs_3') WITH (NUMREPLICA=3); CREATE FILESPACE postgres=# SELECT * FROM pg_filespace_entry; fsefsoid | fsedbid | fselocation ----------+---------+--------------------------------------------- 16384 | 0 | hdfs://Lirong-MBP:9000/gpsql 16532 | 0 | hdfs://Lirong-MBP:9000/hawq/fs_1 16533 | 0 | hdfs://{replica=2}Lirong-MBP:9000/hawq/fs_2 16534 | 0 | hdfs://{replica=3}Lirong-MBP:9000/hawq/fs_3 (4 rows) The {replica=3} option is very confusing. It is not a valid HDSF url, which means we can only access that URL through external tools such as hdfs, although it is valid inside HAWQ (we exclude that part when we are really going to access that path). -- This message was sent by Atlassian JIRA (v6.3.4#6332)