[jira] [Updated] (HAWQ-999) Log_error when file count is not in proportion to bucket number of hash table.
[ https://issues.apache.org/jira/browse/HAWQ-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Espino updated HAWQ-999: --- Labels: (was: ToBeClosed) > Log_error when file count is not in proportion to bucket number of hash table. > -- > > Key: HAWQ-999 > URL: https://issues.apache.org/jira/browse/HAWQ-999 > Project: Apache HAWQ > Issue Type: Improvement > Components: Core >Reporter: Hubert Zhang >Assignee: Hubert Zhang > Fix For: 2.1.0.0-incubating > > > By definition, file count of a hash table should be equal to or a multiple of > the bucket number of the table. So if mismatch happens, we should not treat > it as hash table in data locality algorithm. > The default behaviour should LOG_ERROR and tell the user "file count is not > in proportion to bucket number for hash table with oid=X. Some data maybe > lost, if you still want to continue the query, set GUC > assign_randomly_for_mismatched_hash_table to true and try again." > If GUC assign_randomly_for_mismatched_hash_table is on, the behaviour changed > to treat the hash table as random table in data locality algorithm. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-999) Log_error when file count is not in proportion to bucket number of hash table.
[ https://issues.apache.org/jira/browse/HAWQ-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hubert Zhang updated HAWQ-999: -- Description: By definition, file count of a hash table should be equal to or a multiple of the bucket number of the table. So if mismatch happens, we should not treat it as hash table in data locality algorithm. The default behaviour should LOG_ERROR and tell the user "file count is not in proportion to bucket number for hash table with oid=X. Some data maybe lost, if you still want to continue the query, set GUC assign_randomly_for_mismatched_hash_table to true and try again." If GUC assign_randomly_for_mismatched_hash_table is on, the behaviour changed to treat the hash table as random table in data locality algorithm. was: By definition, file count of a hash table should be equal to or a multiple of the bucket number of the table. So if mismatch happens, we should not treat it as hash table in data locality algorithm. The default behaviour should LOG_ERROR and tell the user "" > Log_error when file count is not in proportion to bucket number of hash table. > -- > > Key: HAWQ-999 > URL: https://issues.apache.org/jira/browse/HAWQ-999 > Project: Apache HAWQ > Issue Type: Improvement > Components: Core >Reporter: Hubert Zhang >Assignee: Hubert Zhang > Fix For: 2.0.1.0-incubating > > > By definition, file count of a hash table should be equal to or a multiple of > the bucket number of the table. So if mismatch happens, we should not treat > it as hash table in data locality algorithm. > The default behaviour should LOG_ERROR and tell the user "file count is not > in proportion to bucket number for hash table with oid=X. Some data maybe > lost, if you still want to continue the query, set GUC > assign_randomly_for_mismatched_hash_table to true and try again." > If GUC assign_randomly_for_mismatched_hash_table is on, the behaviour changed > to treat the hash table as random table in data locality algorithm. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-999) Log_error when file count is not in proportion to bucket number of hash table.
[ https://issues.apache.org/jira/browse/HAWQ-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hubert Zhang updated HAWQ-999: -- Description: By definition, file count of a hash table should be equal to or a multiple of the bucket number of the table. So if mismatch happens, we should not treat it as hash table in data locality algorithm. The default behaviour should LOG_ERROR and tell the user "" was: By definition, file count of a hash table should be equal to or a multiple of the bucket number of the table. So if mismatch happens, we should not treat it as hash table in data locality algorithm. > Log_error when file count is not in proportion to bucket number of hash table. > -- > > Key: HAWQ-999 > URL: https://issues.apache.org/jira/browse/HAWQ-999 > Project: Apache HAWQ > Issue Type: Improvement > Components: Core >Reporter: Hubert Zhang >Assignee: Hubert Zhang > Fix For: 2.0.1.0-incubating > > > By definition, file count of a hash table should be equal to or a multiple of > the bucket number of the table. So if mismatch happens, we should not treat > it as hash table in data locality algorithm. > The default behaviour should LOG_ERROR and tell the user "" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HAWQ-999) Log_error when file count is not in proportion to bucket number of hash table.
[ https://issues.apache.org/jira/browse/HAWQ-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hubert Zhang updated HAWQ-999: -- Summary: Log_error when file count is not in proportion to bucket number of hash table. (was: Treat hash table as random when file count is not in proportion to bucket number of table.) > Log_error when file count is not in proportion to bucket number of hash table. > -- > > Key: HAWQ-999 > URL: https://issues.apache.org/jira/browse/HAWQ-999 > Project: Apache HAWQ > Issue Type: Improvement > Components: Core >Reporter: Hubert Zhang >Assignee: Hubert Zhang > Fix For: 2.0.1.0-incubating > > > By definition, file count of a hash table should be equal to or a multiple of > the bucket number of the table. So if mismatch happens, we should not treat > it as hash table in data locality algorithm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
