Processing file modifications in a networked storage system
Disclosed are various embodiments for processing file modifications in a networked storage system. A file is stored in a file system. If a modification listener is associated with the file, a notification that the file has been modified is sent to the modification listener. The modification listener can trigger processing of the file by executable code.
1. A system, comprising:
a data store including a file system and configuration data; and
a processor in communication with the data store and configured to at least:
store a file in the file system;
determine that a modification listener is associated with the file;
send a notification that the file has been modified to the modification listener; and
wherein, upon obtaining the notification, the modification listener is configured to trigger a processing of the file by executable code, the executable code identified within the configuration data as associated with the file.
2. The system of claim 1 , wherein the executable code, when executed, is configured to obtain the file from the file system in response to the notification.
3. The system of claim 1 , wherein the file is a new version of an existing file in the file system.
4. The system of claim 1 , wherein determining that the modification listener is associated with the file further comprises comparing a file name of the file with a file name associated with the modification listener.
5. The system of claim 1 , wherein determining that the modification listener is associated with the file further comprises comparing a file name extension of the file with a file name extension associated with the modification listener.
6. The system of claim 1 , wherein determining that the modification listener is associated with the file further comprises further comprises comparing a file path of the file with a file path associated with the modification listener.
7. The system of claim 1 , wherein a plurality of modification listeners are associated with the file.
8. The system of claim 1 , wherein the executable code corresponds to a service.
9. A method, comprising:
storing, by at least one computing device, a new version of a file in a file system;
determining, by at least one computing device, that a modification listener is associated with the file in response to obtaining a polling request from the modification listener;
sending, by the at least one computing device, a notification that the file has been modified to the modification listener; and
wherein, upon obtaining the notification, the modification listener is configured to trigger a processing of the file by executable code identified within configuration data as associated with the file.
10. The method of claim 9 , wherein storing the new version of the file further comprises storing the new version of the file in an eventually consistent data store and a cache.
11. The method of claim 9 , further comprising receiving, by at least one computing device, a new version of the file from a client over a network.
12. The method of claim 9 , wherein the file system is a metadata-based file system, wherein metadata for the file is organized separately from data for the file.
13. The method of claim 9 , wherein the executable code is a service, and the service is configured to obtain the new version of the file from the file system in response to the notification.
14. The method of claim 13 , wherein the notification includes at least one access parameter for the service.
15. A system, comprising:
a data store including a file system and configuration data; and
a processor in communication with the data store and configured to at least:
store a file in the file system;
determine that a modification listener is associated with the file in response to obtaining a polling request from the modification listener;
send a notification that the file has been modified to the modification listener; and
wherein, upon obtaining the notification, the modification listener is configured to trigger a processing of the file by executable code identified within the configuration data as associated with the file.
16. The system of claim 15 , wherein the file is a new version of an existing file in the file system.
17. The system of claim 15 , wherein the notification comprises a starting offset indicating where changes to the file have occurred.
18. The system of claim 15 , wherein the executable code is a service, and the service is configured to obtain the file from the file system in response to the notification.
19. The system of claim 15 , wherein the file is received from a client over a network.
20. The system of claim 19 , wherein the client is configured to present the file system to a user through a same interface as a locally attached storage of the client.